Model Context Protocol (MCP) Servers

Extend BB's capabilities by connecting to a wide range of external tools and services through Model Context Protocol servers.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows BB to securely connect with external tools, systems, and data sources through standardized servers. With MCP support, BB can:

  • Access external APIs and services
  • Connect to databases and data platforms
  • Interact with specific tools like GitHub, Slack, or Google Drive
  • Access specialized functionality for different professional areas of expertise
  • Perform tasks that require secure access to external systems

Key Benefits:

  • Extends BB's capabilities beyond its built-in functionality
  • Provides secure, controlled access to external tools
  • Supports hundreds of different integrations through community servers
  • Enables advanced workflows that span multiple systems
  • Maintained by a growing community of developers and organizations

Local vs Remote MCP Servers

BB supports two types of MCP server connections, each suited to different use cases:

Local MCP Servers

Run as processes on your machine, connecting via STDIO (standard input/output).

Best for:

  • Accessing local files and databases
  • Running custom tools and scripts
  • Development and testing
  • Maximum privacy and control

Remote MCP Servers

Hosted services accessed via HTTP/HTTPS, often with OAuth authentication.

Best for:

  • Connecting to cloud services (Slack, Google Drive, etc.)
  • Accessing company systems and APIs
  • No local installation required
  • Secure OAuth-based authentication

Pro Tip: Use local servers for file system access and development tools, and remote servers for cloud services and team integrations. You can use both types simultaneously in the same project.

Remote MCP Servers

Remote MCP servers eliminate the need for local installation—connect to hosted services with just a URL. Perfect for integrating cloud services, company systems, and specialized tools directly into your BB workflow.

Why Use Remote MCP Servers?

  • Zero Installation: No software to download or manage—just add the server URL
  • Secure OAuth Access: Connect to private services (Slack workspaces, company systems, research databases) with one-click authentication
  • Team Context: Access shared team resources and collaboration tools without leaving BB
  • Growing Ecosystem: Hundreds of servers available for knowledge work, research, and business systems

Finding Remote MCP Servers

Browse these directories to discover servers for your workflow:

Common Use Cases:

  • Team collaboration: Pull Slack threads or meeting notes into your project context
  • Research workflows: Access academic databases or specialized search engines
  • Business systems: Connect to CRMs, HR platforms, or project trackers
  • Calendar intelligence: Coordinate schedules without switching apps

Available MCP Servers

BB supports a wide range of MCP servers across different categories:

File and Data Access

  • Filesystem: Access and manage files with configurable permissions
  • Google Drive: Search and access files stored in Google Drive
  • Database Connectors: Connect to PostgreSQL, MySQL, SQLite, MongoDB, and other databases
  • Vector Databases: Integrate with Chroma, Qdrant, Pinecone for vector search

Development and Collaboration

  • Git: Manage local Git repositories
  • GitHub/GitLab: Access repositories, issues, PRs, and other platform features
  • Slack: Read from and post to Slack channels
  • Docker: Manage Docker containers and images
  • Kubernetes: Interact with Kubernetes clusters

Research and Content

  • Web Search: Search the web using various search engines
  • Fetch: Retrieve and process web content
  • Memory: Store and retrieve information across conversations
  • EverArt: Generate images using various AI models

Analysis and Visualization

  • Visualization Tools: Create charts, graphs, and visualizations
  • Data Processing: Handle and transform data in various formats
  • Time Series Analysis: Work with time-based data

Growing Ecosystem: The MCP ecosystem continues to grow with new servers being added regularly. For the most up-to-date list of available servers, visit the MCP GitHub repository.

Configuring MCP Servers

MCP servers belong to a workspace. You add a server once, and every project in that workspace can then choose to use it. This keeps connections to outside services in one place, where the people responsible for the workspace can look after them.

Adding a Server to Your Workspace

  1. Open Settings and choose Workspace, then the Connections tab
  2. In the MCP Servers section, click Add Server
  3. Fill in the server's details (see below) and save
  4. If the server uses OAuth, click Authorize next to it in the list to sign in
MCP Servers section with Airtable (STDIO transport, npx -y airtable-mcp-server, 1 environment variable) and Canva (HTTP transport, Auth Complete, Re-authorize), and Add Server
MCP servers for the workspace

Who Can Manage Servers

Team leads and owners of the workspace's team (and organization owners and admins) can add, change or remove a workspace's MCP servers.

Other members see the list read-only. They can still click Authorize to sign in to a server for themselves. Organization owners and admins can see and manage the MCP servers of every shared workspace.

Using a Server in a Project

There's no separate MCP setting in a project. Each authorized server appears as a tool set, so a project includes a server by selecting that server's tool set:

  1. Open the project's settings
  2. Go to the Tools tab
  3. Under Tool Sets, select the tool set for the server

To make a server available to every new project, select its tool set in the workspace's Project Defaults instead. See Tools for more on tool sets.

Server Configuration Details

Each MCP server has specific configuration options depending on its transport type:

Transport Type

Choose how BB connects to the MCP server:

  • STDIO (Local Process): Runs the server as a local process on your machine. Requires the server software to be installed locally.
  • HTTP (Remote Server): Connects to a hosted MCP server via HTTPS. No local installation required—just provide the server URL.

Configuration Fields

  • Server ID: Unique identifier for the server (e.g., "slack", "github-work")
  • Display Name: Human-readable name shown in the UI
  • Command (STDIO only): The command to run the local server process
  • Arguments (STDIO only): Command-line arguments passed to the server
  • Server URL (HTTP only): The HTTPS endpoint for the remote server (e.g., "https://mcp.slack.com")
  • Environment Variables: Key-value pairs providing configuration or secrets (both transport types)

Saved secrets stay hidden. Keys, tokens and passwords in an MCP server's settings are stored encrypted and only ever shown masked. They can't be read back: to change one, type a new value.

OAuth Authentication

Remote MCP servers often require OAuth for secure access to private services. BB supports two OAuth configuration methods:

Automatic OAuth (Recommended)

Turn on OAuth in the OAuth Configuration section when adding a remote server. BB automatically discovers the authentication requirements from the server and guides you through the secure login process:

  1. BB queries the MCP server for its OAuth configuration
  2. A secure login window opens from the third-party provider (similar to "Sign in with Google")
  3. You complete the login and grant BB access to your account
  4. The server's entry in the list shows a green "Auth Complete" status badge
Servers That Need a Client ID

Some servers don't let BB register itself with them automatically. Their entry in the list shows ⚠️ Config needed, and signing in fails until you give BB a client ID from the service provider. While the Client ID field is empty, it says "(Will be auto-registered if supported)".

  1. In the provider's developer portal, create an app or integration for BB.
  2. Register BB's redirect URL with it: https://chat.beyondbetter.app/oauth/mcp/<server-id>/callback, where <server-id> is the server's Server ID. If you run your own copy of the BB app, use its address in place of https://chat.beyondbetter.app.
  3. Copy the provider's client ID, and its client secret if it gives you one.
  4. In BB, click Edit on the server and enter them as the Client ID and Client Secret in the OAuth section ("PKCE Configuration (Secure)"). Save, then click Authorize.

Example: Canva. With the Server URL https://api.canva.com/connect/v1/mcp and Server ID canva, create a Canva Connect integration, add the redirect URL https://chat.beyondbetter.app/oauth/mcp/canva/callback, and enter its client ID and secret in BB.

Add New MCP Server dialog with Server ID, Display Name, Transport Type set to HTTP (Remote Server), Server URL and the OAuth Configuration section
Adding a remote MCP server with automatic OAuth configuration
Edit Airtable dialog for a local (STDIO) server: Command npx, Arguments -y and airtable-mcp-server, and the AIRTABLE_API_KEY environment variable with its saved value hidden
Editing a local MCP server; saved values aren't shown

Using MCP Servers

Once configured, BB automatically detects and uses the appropriate MCP servers based on your requests:

Example Interactions

Accessing GitHub:

"Can you check the open issues in my repository and summarize the most critical ones?"

Web Research:

"Find the latest research papers on quantum computing from the past year and create a summary of key advances."

Database Analysis:

"Connect to my PostgreSQL database and analyze customer purchase patterns over the last quarter."

Common Use Cases

  • Research: Web search, academic database access, and literature review
  • Development: Code repository management, issue tracking, and code analysis
  • Content Creation: Image generation, content research, and multi-media processing
  • Data Analysis: Database querying, visualization creation, and report generation
  • Communication: Drafting emails, posting to Slack, and chat interactions

Signing In to MCP Servers

Some servers work with each person's own account, such as your own Slack or Google login. For these, everyone signs in for themselves, so BB only ever reaches the service as you, with your access. Until you sign in, that server's tools aren't available to you, and the LLM knows which servers are waiting for you.

Before You Start

When a project uses servers you haven't signed in to yet, a notice above the chat input says "Some tools need you to sign in" and lists each server with a Sign in button. You can sign in straight away, or ignore the notice and carry on: it never stops you sending a message, and you can hide it.

Notice above the message input: Some tools need you to sign in. Canva: Sign in to use its tools in this chat, with a Sign in button
Signing in to an MCP server from the chat

When BB Needs a Server

If BB tries to use one of these tools before you've signed in, the conversation shows a card, "Sign in to <server>", with two buttons:

  • Sign in opens the service's sign-in window. Once you're done, the card says "You're signed in. Continuing..." and BB carries on with the same step.
  • Not now skips it. BB continues without that tool.

BB waits up to 10 minutes for you to sign in. If a step failed because you weren't signed in, its entry in the conversation also offers Sign in to <server> to the person whose request it was.

In a Shared Conversation

Only the person who has to sign in sees the buttons. Everyone else in the conversation sees "Waiting for <name> to sign in to <server>." Nobody can sign in on someone else's behalf.

Being Asked Again

Sign-ins don't last forever. If the service refuses to renew your sign-in, BB clears it and asks you to sign in again the next time it needs that server.

Signed In, but the Tools Still Aren't There

You may see this after signing in:

"You're authorized, but this server's tools aren't in the workspace's tool sets yet. A team lead or owner can add them by authorizing the server."

Your sign-in worked, but the workspace doesn't offer the server's tools yet. Ask a team lead or owner to click Authorize for the server in Settings > Workspace > Connections.

MCP Servers and Agent Accounts

In shared team workspaces, agents can run as an agent account instead of as the person who started them. An agent account isn't a person, so it can't sign in to a service for itself. Agents running as an account can only use MCP servers that need no per-person sign-in. For the others, BB shows:

"Not available to <account>: this server only works with each person's own sign-in, which service accounts can't use."

See Agent Accounts: MCP servers for more.

Adding Custom MCP Servers

Advanced users can create and configure custom MCP servers for specific requirements:

  1. Install the desired MCP server following its documentation
  2. Add the server in Settings > Workspace > Connections
  3. Configure necessary parameters, paths, and environment variables
  4. Test the server with simple queries

Security Considerations:

  • Only use MCP servers from trusted sources
  • Review the permissions and access level of each server
  • Use environment variables for sensitive information (BB stores saved values encrypted and shows them masked)
  • Regularly update MCP servers to their latest versions

Custom MCP Server Development

Need BB to connect to your company's specific systems? We can build custom MCP servers tailored to your workflow and business requirements.

What We Can Build

  • Custom integrations with proprietary company systems
  • CRM and business platform connectors
  • Internal tool and database access
  • Specialized research or analysis tools
  • Industry-specific workflow integrations

Our Expertise

  • Production-grade infrastructure used in BB itself
  • OAuth and enterprise authentication support
  • Secure, reliable server implementation
  • Full documentation and ongoing support

Interested in a custom MCP server for your organization?

Contact Us About Custom Development

We also maintain the Beyond MCP Server library—the same production-grade infrastructure powering BB's MCP capabilities.

Related Documentation

Last updated: November 18, 2026