Skip to main content

Configuring MCP servers for your organization

Organization admins can enable, configure, and manage MCP server integrations for their entire organization. Once configured at the organization level, agent creators can connect these integrations to individual agents without needing to set up credentials themselves.

Accessing MCP server settings​

  1. Navigate to Organization > Connectors in the left sidebar, or go directly to https://devs.ai/org-connectors.
  2. The Connectors page lists all available MCP server integrations and any custom servers you have created.

From this page, you can:

  • Enable pre-built integrations from templates
  • Create custom MCP server connections
  • Edit or delete existing connections
  • Control which connectors are available in agent chat

Enabling a pre-built integration​

The platform provides ready-to-use templates for popular services such as Slack, Google Calendar, Gmail, Jira, and others.

  1. On the Connectors page, browse the list of available templates.
  2. Click Enable on the integration you want to set up.
  3. Configure authentication (see Authentication Options below).
  4. Review the list of available tools and select the ones your organization needs.
  5. Click Save.

Once enabled, the integration becomes available for agent creators in your organization to connect to their agents.

Creating a custom MCP server​

If you need to integrate with an internal system or a service that does not have a pre-built template, you can create a custom MCP server connection.

  1. On the Connectors page, click Create Custom.
  2. Enter a Server Name to identify the connection.
  3. Provide the Server URL — the endpoint where your MCP server is running.
  4. Optionally upload a Logo to make it easier to identify.
  5. Choose an authentication type and complete the guided steps (for many servers, especially OAuth, the product detects what is needed and fills in fields for you).
  6. Click Save.

After saving, the platform connects to your MCP server, discovers available tools, and lists them for you. You can then select which tools to make available.

📝 Note: Custom MCP servers must be accessible over HTTPS. Only URL-based (remote) MCP servers are supported — local or stdio-based servers cannot be connected directly.

Authentication options​

When configuring an MCP server, you choose how the platform authenticates with the external service.

OAuth (streamlined setup for custom MCP)​

When you connect a custom MCP URL, Devs.ai can usually detect OAuth requirements from the server and walk you through setup in a few steps:

  • OAuth is auto-detected from the MCP endpoint where the protocol exposes it.
  • OAuth clients can register dynamically (dynamic client registration), so you often avoid copying a Client ID and Client Secret out of a vendor console.
  • Fields auto-populate when the server and flow allow it—follow the on-screen prompts as the source of truth for your connection.
  • Tokens and tool calls are handled more safely, including stronger protections against unsafe server-side requests when tools run.

For many MCP servers, that means connecting in a few clicks instead of a long manual configuration. If your server or security policy still needs static OAuth app credentials, the UI will ask for them when required.

OAuth (pre-built templates and provider-specific guides)​

Pre-built integrations (Slack, Google, Atlassian, GitHub, Dropbox, and others) still follow each vendor’s expectations. Often you will create an OAuth app in the provider’s console and paste Client ID and Client Secret into the connector, because the template is tied to your organization’s app registration.

With OAuth in general:

  • Each user authorizes access to their own account the first time they use the integration (where the flow is per-user).
  • The platform stores and refreshes tokens securely.

For step-by-step OAuth setup, see the individual server pages:

API key​

For services that authenticate using a static API key:

  1. Select API Key as the authentication type.
  2. Enter the API key value.
  3. The key is encrypted and stored securely by the platform.

Pass-through headers​

For internal services that accept the same credentials your users already send to Devs.ai (such as SSO tokens or internal API keys):

  1. Select Pass-Through Headers as the authentication type.
  2. Configure which headers should be forwarded to the MCP server.

For more details, see Pass-through headers authentication.

None​

For MCP servers that do not require authentication (for example, public or internal endpoints on a private network).

Managing connectors​

Enabling and disabling​

Each connector has two toggle controls:

  • Enabled — Controls whether the connector is active for the organization. When disabled, no agents can use it.
  • Enable in Chat — Controls whether the connector is available during agent chat sessions. When enabled, a chat tool is created and agents can actively use the connector's tools.

Editing a connector​

Click Edit on any connector to update its authentication credentials, URL, or selected tools.

Deleting a connector​

Click Delete to remove a connector. This disconnects it from all agents that were using it.

Selecting tools​

For both pre-built and custom connectors, you can control which tools are available to agents. Each tool represents a specific capability (such as reading messages, creating issues, or listing files). Deselecting tools you do not need helps keep agent behavior focused and reduces unnecessary API calls.

📝 Note: Each MCP server connection supports up to 100 selected tools.

Security​

  • OAuth tokens and API keys are encrypted at rest using AES-256-GCM encryption.
  • OAuth tokens are stored per-user — each user's authorization is independent.
  • Credentials are never exposed in the admin UI after they are saved.
  • Pass-through headers exist only for the duration of the request and are never stored.
  • MCP tool calls are executed with additional safeguards (for example, stronger handling of server-side request risks) so a misbehaving remote server is less likely to abuse the integration.

Next steps​

Once your organization has MCP servers configured, agent creators can connect them to individual agents. See Configuring extended capabilities for instructions on linking MCP servers to agents and selecting which tools each agent can use.

⌘J