> ## Documentation Index
> Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP
> Connect agents to external tools and services via the Model Context Protocol.
MCP (Model Context Protocol) lets agents use tools outside your repository: Datadog, Linear, Slack,
Notion, Sentry, and other services. Configure MCP servers from Settings -> Repositories -> \[repo] ->
MCP Servers.
[Skills](/customizing-agents/skills) and [plugins](/customizing-agents/plugins) shape what the agent
knows and how it behaves. MCP expands what the agent can reach.
## How it works
Add MCP servers from the catalog, or add a custom server by URL or local command. Each server is
scoped in one of two ways:
* **This repo**: shared with everyone using the repository.
* **Just for you**: available only to tasks you start in that repository.
Shared servers do not automatically share personal OAuth accounts. If a teammate uses a shared OAuth
server, they connect their own account. API-key servers read secrets from repository **Agent**
environment variables.
The Connected section shows what is enabled for the repo and what is enabled for you. For shared
servers, you can opt out for yourself; repo admins can also disable the shared default. Disabled
servers are not included in the agent's MCP config for your tasks.
## Auth
Remote MCP servers use one of three auth modes:
* **OAuth**: connect your account through the provider's OAuth flow. For custom servers, this only
works when the server supports
[Dynamic Client Registration (DCR)](https://workos.com/blog/dynamic-client-registration-dcr-mcp-oauth).
Niteshift stores the token for your user and refreshes it when the provider allows refresh.
* **API key**: store the secret as a repository **Agent** environment variable. Niteshift passes it
to the MCP server through headers such as `Authorization`.
* **No auth**: no credentials are needed. Niteshift can detect this for custom remote servers that
do not advertise OAuth metadata.
Local `stdio` servers run inside the task environment and use a command, args, and optional env
values instead of OAuth.
## Catalog
The catalog has pre-built configs for common services. Search for a provider, choose a scope, and
pick an auth method if the provider supports more than one. OAuth providers start the connect flow
after you add them. API-key providers show the required **Agent** env vars and report `Missing keys`
until those vars are saved.
| Provider | What the agent can reach |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| 
Amplitude | Events, users, cohorts |
| 
Atlassian | Jira issues and Confluence pages |
| 
Braintrust | Projects, experiments, evaluation logs |
| 
Buildkite | Pipelines, builds, annotations |
| 
Context7 | Up-to-date docs for libraries and frameworks |
| 
Datadog | Metrics, APM, logs, monitors |
| 
Granola | Meeting notes and decisions |
| 
Hex | Notebooks, projects, data workspaces |
| 
Hugging Face | Models, datasets, spaces |
| 
LangSmith | LLM traces, datasets, evaluations |
| 
LaunchDarkly | Feature flags, experiments, AI configs |
| 
Linear | Issues, projects, cycles, and comments |
| 
Neon | Postgres branches, databases, queries |
| 
Notion | Pages, databases, and comments |
| 
PlanetScale | Databases, branches, schema, insights |
| 
Postman | Collections, tests, mocks, API specs |
| 
PostHog | Events, funnels, feature flags |
| 
Render | Deployments, services, logs |
| 
Sanity | Content, schemas, datasets |
| 
Sentry | Errors, performance, and releases |
| 
Slack | Messages, channels, canvases |
| 
Sourcegraph | Code search across repositories |
| 
Stripe | Payments, customers, subscriptions |
| 
Supabase | Postgres, auth, storage |
| 
Webflow | CMS, sites, asset management |
**Coming soon**:
## Custom servers
Use **Add custom server** when the catalog does not include the service you need.
* **No auth**: select `http` or `sse`, enter the URL, and leave headers blank. If the server does
not advertise OAuth metadata, Niteshift marks it `No auth`.
* **OAuth**: select `http` or `sse`, enter the URL, and leave headers blank. If the server
advertises OAuth metadata and supports DCR, Niteshift redirects you to authorize the connection.
* **API key**: add the secret as an **Agent** env var, then reference it in headers with
`${ENV_VAR}`.
```txt theme={"dark"}
Authorization=Bearer ${ACME_MCP_TOKEN}
X-Workspace=${ACME_WORKSPACE_ID}
```
For a local MCP server, choose `stdio` and provide the command, args, and optional env values. Make
sure your setup script installs any package or binary the command needs.
## Config preview
Niteshift writes the right config format for each agent: JSON for Claude Code and TOML for Codex.
The settings page includes a read-only raw config preview so you can inspect what each agent will
receive.
Asana
Figma
Vercel