TaskieLog in / Sign up
Taskie Help

Set up the ready-made MCP servers

Step-by-step setup for each ready-made MCP server in the App Center, from Slack, Notion, and GitHub to Mattermost, with the right sign-in method for each.

This guide walks through each ready-made MCP server in the App Center: what to turn on where, which token to create, and which sign-in method to choose so Taskie's agent can use that service's tools. A shorter version of the same steps also appears next to each server's connect form in the App Center.

Before you start

Only a workspace admin can connect an external MCP server, and the feature depends on your workspace plan. Open the App Center, go to MCP servers, and pick a server. Its URL and recommended authentication method are filled in for you, so you only complete the sign-in details.

  • Sign in automatically: the quickest option for servers that support it, such as Notion, Linear, GitLab, Stripe, Sentry, and Cloudflare. Taskie registers itself with the service, and you just approve access on the service's sign-in page. You don't need to create an OAuth app.
  • Own OAuth app: for services without automatic registration, such as Slack and Google. You create an OAuth app in the service, add the redirect URI shown in the form, and enter the Client ID and Client Secret.
  • Token or header: for services that accept an API key or personal token. Create the token and paste it into the form. All credentials are stored encrypted.
  • Turn tools on: after connecting, discovered tools are usually off. Open the connection and turn on only the tools the agent may use.
  • Network route: the platform picks how each server is reached. For a self-hosted server, you can pin the route to Direct or Via proxy under Advanced settings.

Slack

Server URL: https://mcp.slack.com/mcp

  1. Go to api.slack.com/apps, choose Create New App → From scratch, and pick your workspace.
  2. In the app sidebar open Agents and turn on “Slack Model Context Protocol (MCP) Server”.
  3. Under OAuth & Permissions, add the redirect URL shown below and the user token scopes listed in the Scopes field.
  4. From Basic Information, copy the Client ID and Client Secret into “Own OAuth app”, then choose Connect with OAuth and approve.

Slack only lets internal apps or Marketplace apps use its MCP server. A workspace admin may need to approve the app first.

Mattermost

Server URL: https://your-server/plugins/mattermost-ai/mcp-server/mcp

  1. On your Mattermost server (version 11.2 or later), update the Agents plugin to its latest version.
  2. In System Console → Plugins → Agents → Model Context Protocol (MCP), set “Enable Mattermost MCP Server (HTTP)” to True.
  3. Enter the Server URL as https://your-server/plugins/mattermost-ai/mcp-server/mcp.
  4. For a token: enable Personal Access Tokens in System Console → Integrations → Integration Management, then create one under Profile → Security → Personal Access Tokens and paste it as the Bearer token.
  5. To sign in instead: turn on “OAuth 2.0 Service Provider” and “OAuth 2.0 Dynamic Client Registration” in Integration Management, then choose OAuth 2.0 → Sign in automatically.

The agent acts with the permissions of the account whose token or sign-in you use.

Notion

Server URL: https://mcp.notion.com/mcp

  1. Choose OAuth 2.0 → Sign in automatically and select Connect.
  2. Sign in to Notion, pick the workspace and the pages to share, and approve.

Notion’s MCP server accepts sign-in only; internal integration secrets don’t work with it.

Google Calendar

Server URL: https://calendarmcp.googleapis.com/mcp/v1

  1. Make sure your Google Workspace is enrolled in the Workspace Developer Preview Program, since this server is in preview.
  2. In Google Cloud Console, enable the Google Calendar API and the Calendar MCP API (calendarmcp.googleapis.com).
  3. In Google Auth Platform, set up Branding and Audience, and add the scopes from the Scopes field under Data Access.
  4. Under Clients, create a Web application client and add the redirect URI shown below.
  5. Paste the Client ID and Client Secret into “Own OAuth app” and connect.

Google Drive

Server URL: https://drivemcp.googleapis.com/mcp/v1

  1. Make sure your Google Workspace is enrolled in the Workspace Developer Preview Program, since this server is in preview.
  2. In Google Cloud Console, enable the Google Drive API and the Drive MCP API (drivemcp.googleapis.com).
  3. In Google Auth Platform, set up Branding and Audience, and add the scopes from the Scopes field under Data Access.
  4. Under Clients, create a Web application client and add the redirect URI shown below.
  5. Paste the Client ID and Client Secret into “Own OAuth app” and connect.

The agent sees only what the signing-in account can see in Drive.

Linear

Server URL: https://mcp.linear.app/mcp

  1. Choose OAuth 2.0 → Sign in automatically, select Connect, and approve in Linear.
  2. Or create a personal API key in Linear → Settings → Account → Security & Access, choose Bearer token and paste it.

For read-only access, give the API key only the Read permission.

GitHub

Server URL: https://api.githubcopilot.com/mcp/

  1. In GitHub → Settings → Developer settings → Personal access tokens, create a fine-grained token for the repositories you need.
  2. Paste it as the Bearer token and connect.
  3. Or use an OAuth app: under Developer settings → OAuth Apps → New OAuth App, set the callback URL to the redirect URI shown below, then paste its Client ID and Client Secret into “Own OAuth app”.

GitHub Enterprise Server has no hosted MCP server.

GitLab

Server URL: https://gitlab.com/api/v4/mcp

  1. On GitLab.com, a top-level group Owner allows MCP clients under Settings → General → Permissions and group features → MCP client access. On a self-managed instance, an administrator enables it.
  2. For a self-managed instance, replace gitlab.com in the Server URL with your own host.
  3. Choose OAuth 2.0 → Sign in automatically, select Connect, and approve in GitLab.

GitLab’s MCP server is in beta.

Stripe

Server URL: https://mcp.stripe.com

  1. An account admin allows MCP access at dashboard.stripe.com/settings/mcp-and-cli-access.
  2. Choose OAuth 2.0 → Sign in automatically, select Connect, and approve in Stripe.
  3. Or, in Developers → API keys, create a restricted key with “Authorize agent access to your account” and paste it as the Bearer token.

From 31 October 2026, Stripe’s MCP server rejects full secret keys and ordinary restricted keys; use an agent key. Try a test-mode key first.

Sentry

Server URL: https://mcp.sentry.dev/mcp

  1. Choose OAuth 2.0 → Sign in automatically, select Connect, and approve in Sentry.
  2. Or create a personal token in Sentry → User Settings → Personal Tokens with the org:read and project:read scopes.
  3. Choose Custom header, keep the header name Authorization, and enter the value as “Sentry-Bearer your-token”.

A plain Bearer token won’t work: Sentry reserves it for its own sign-in. Self-hosted Sentry isn’t supported by the hosted server.

Cloudflare

Server URL: https://mcp.cloudflare.com/mcp

  1. Choose OAuth 2.0 → Sign in automatically, select Connect, and approve in Cloudflare.
  2. Or create an API token at dash.cloudflare.com/profile/api-tokens with only the permissions you need, choose Bearer token and paste it.

Product servers such as observability.mcp.cloudflare.com/mcp can be added with Custom server. Tokens with IP filtering aren’t supported.

AWS Knowledge

Server URL: https://knowledge-mcp.global.api.aws

  1. No sign-in is needed: keep “No authentication” and select Connect.
  2. The tools search AWS documentation, regional availability and best practices.

This server can’t reach your AWS account. The account-level AWS MCP Server needs a local signing proxy, which isn’t supported here.

Zapier

Server URL: https://mcp.zapier.com/api/v1/connect

  1. At mcp.zapier.com, create an MCP server, choose “Other” as the client, and add the actions you want.
  2. Open Connect, generate a token (it’s shown once), choose Bearer token and paste it.
  3. Or choose OAuth 2.0 → Sign in automatically.

Each tool call uses two Zapier tasks.

If the connection fails

  • 401 or 403 errors: the token expired or lacks access. Create a new token or sign in again with OAuth, then choose Check again.
  • "This server doesn't ask for sign-in": the server works without authentication, so choose No authentication.
  • "This server doesn't support automatic sign-in": use Own OAuth app or Paste a token instead.
  • Connection errors or timeouts: check the server URL. For a self-hosted server, switch the network route on the connection page between Direct and Via proxy, then check again.
  • Tools don't work: make sure the tools you need are turned on in the connection. The agent can't see tools that are off.

For an overview of the feature, read Connect external MCP servers to the agent, and for tool risk levels and approval before running, see the "Manage MCP tools and safety" guide.

Was this article helpful?