> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/setup-nimbalyst/mcp.md).

# MCP

Add MCP servers to Nimbalyst so your coding agent can reach GitHub, Linear, Slack, and other services. Covers install, config, and permissions.

MCP (Model Context Protocol) servers extend what your coding agent can do in Nimbalyst. They give your agent access to external services like GitHub, Linear, Slack, and more. Add one when you want the agent to work with a tool you already use.

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2FJ1pBc9XDlJuxIRdclLDe%2Fimage.png?alt=media&amp;token=a0765aba-4f66-4128-826b-1c75aa29fd5d" alt="The MCP Servers settings page showing the Add MCP Server template gallery"><figcaption><p>The MCP Servers settings page, with the template gallery for adding a server.</p></figcaption></figure>

### What Are MCP Servers?

MCP servers are connectors that let your coding agent interact with other apps and services. When you connect an MCP server, the agent gains new abilities like:

* Creating issues in Linear
* Searching your GitHub repositories
* Querying your database
* Accessing files in Google Drive

For setup walkthroughs and a list of servers worth connecting, see [Claude Code MCP setup](https://nimbalyst.com/blog/claude-code-mcp-setup/) and [best Claude Code MCP servers](https://nimbalyst.com/blog/best-claude-code-mcp-servers/).

### Built-in MCP Tools

Nimbalyst ships its own MCP tools that any agent can call to interact with the editor:

* **AskUserQuestion**: pops up one or more multiple-choice questions in the transcript and blocks the agent until you answer.
* **PromptForUserInput**: collects several inputs at once through a single structured-prompt widget. Five field types are available: multi-select, single-select, reorder, edit-text, and confirm. Voice mode honors a `voiceFriendly` hint and defers to the screen widget for long drafts or large reorders. See [Interactive Prompts](/session-management/interactive-prompts.md) for examples and trigger phrases.
* **display\_to\_user** / **capture\_editor\_screenshot**: render charts, images, or screenshots inline in the transcript.
* **developer\_git\_commit\_proposal**: surfaces the interactive commit proposal widget instead of running `git commit` from a shell.

### Calling a Configured MCP Server from Chat

Just refer to the MCP server in your chat and your coding agent will figure out you need to use it.

For example:

* "Add these to a Linear ticket"
* "Analyze this cohort in PostHog"

### Application vs Project Servers

You can configure servers at two levels:

**Application**

* Available in all your projects
* Good for personal tools you always want access to
* Example: Your personal GitHub account
* Configure under **Settings > Application > MCP Servers**

**Project**

* Only available in a specific project
* Good for project-specific services
* Example: A project's database connection
* Configure under **Settings > Project > MCP Servers**

Project servers receive the current repository as their scope and do not automatically appear in other workspaces. See [Application, Account, and Project Settings](/setup-nimbalyst/settings-scopes.md).

### Node Runtime for MCP Servers

MCP servers configured with `command: "node"` use Electron's bundled Node runtime. You don't need a system-wide Node.js install for MCP servers to work on a fresh Nimbalyst install.

### Adding MCP Servers

1. Open **Settings** with the account menu or `Cmd/Ctrl+,`.
2. Choose **Application > MCP Servers** or **Project > MCP Servers**.
3. Click **Add Server**.
4. Choose from a template or configure manually.
5. If the server requires credentials, enter them: for **API key** servers, paste the key into the server settings; for **OAuth** servers, click **Authorize** and sign in through your browser.

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2FJPvp36JRiYToq72WcUsG%2Fimage.png?alt=media&amp;token=8009d9e6-bcb5-4575-afa0-2dc5e391edbc" alt="The GitHub MCP server template configuration with a personal access token field, Test Connection, and Add Server button"><figcaption><p>Configuring the GitHub template: enter the required credential, test the connection, then add the server.</p></figcaption></figure>

#### Available Templates

Nimbalyst includes ready-to-use templates for popular services, grouped by category in the gallery. They include:

* **Development**: GitHub, Playwright, Chrome DevTools, Context7, Serena, Sentry
* **Productivity**: Linear, Notion, Asana, Atlassian (Jira and Confluence), Slack
* **Data & Analytics**: PostHog, Snowflake, AWS, Stripe
* **Design**: Figma
* **Search & Files**: Brave Search, Fetch, Filesystem

More templates ship over time; use the search field in the gallery to find one.

### Checking Server Status

In the MCP Servers settings, each server shows its status:

* **Connected**: Working and ready to use
* **Not authorized**: Needs authentication (click Authorize)
* **Error**: Something went wrong (check the error message)

### Troubleshooting

**Server not appearing in your agent's tools?**

* Make sure the server is enabled (not disabled)
* Check that authentication is complete
* Try restarting Nimbalyst

**OAuth authorization failed?**

* Complete the sign-in process in your browser
* Try revoking and re-authorizing
* Check your internet connection

**API key not working?**

* Verify the key is correct (no extra spaces)
* Check that the key has the required permissions
* Some services require specific scopes or access levels

### Privacy & Security

* All MCP connections are made locally from your computer
* API keys and tokens are stored securely on your machine
* OAuth tokens can be revoked at any time from settings
* No credentials are sent to Nimbalyst servers


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/setup-nimbalyst/mcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.