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.

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 and 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 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.

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

Some servers require authentication:

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

Available Templates

Nimbalyst includes ready-to-use templates for popular services:

• GitHub - Work with repositories, issues, and pull requests

• GitLab - DevOps and repository management

Productivity

• Linear - Issue tracking and project management

• Notion - Access your workspace and pages

• Asana - Task management

• Atlassian - Jira and Confluence

Data & Analytics

• PostgreSQL - Query databases

• PostHog - Product analytics

Design

• Figma - Access Figma designs and assets

Search

• Brave Search - Web search capabilities

Files

• Google Drive - Access your documents

• Filesystem - Access local files

From the Settings Panel

• API Key: Enter your API key in the server settings

• OAuth: Click "Authorize" and sign in through your browser

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