Skip to main content
GitHub, Slack, and Linear are wired in directly. Everything else — databases, browser automation, third-party APIs — comes through MCP servers. Add and manage them under Settings → Connectors in the Cosmos menu, including partner servers like Atlassian, Sentry, Stripe, and Figma. If your menu shows MCP Registry under Settings → Capabilities, use that page instead.

​
Managing MCP Configurations

​
Updating or Removing

Open a configured MCP server to update its credentials, manage access, or delete it when you no longer need it.

​
Sharing an MCP Server

Manage access controls who can use the MCP configuration. To give everyone in your organization use access:
  1. Open the configured server under Connectors, then choose Sharing → Manage access. In the MCP Registry, use the server’s menu → Manage access.
  2. In the sharing dialog, set General access → Organization access to Can use. In versions that label the organization-wide row Everyone, choose Can use there: Everyone → Can use means everyone in your organization, not the public internet.
  3. Save the changes and complete any connection-sharing confirmation. To share with fewer people, add only the intended people, groups, or service accounts with Can use instead.
If the dialog offers Individual accounts or Shared connection, choose deliberately: individual accounts require each recipient to connect their own account; a shared connection lets recipients use the configured account. Only share a service account’s connection with people who should have its downstream permissions.
Older screens and screenshots may show a Shared toggle or user/tenant scope. In the access-based UI, use Manage access to confirm grants; a legacy scope label does not tell you who can use the server. If you cannot manage access, ask the configuration owner to grant it.

​
Referenced Secrets Need Separate Access

For a generic secret referenced from the server configuration, such as $augment-MY_API_KEY, configure the secret’s access separately. Do not assume that sharing the MCP configuration also grants access to that secret.
  1. Open the referenced secret in Secrets, then Sharing → Manage access (or the secret’s menu → Share).
  2. Grant Can use to the people or service accounts that will run the sessions. For organization-wide use, grant it to the organization as well as on the MCP configuration.
  3. Check the secret’s Used in settings: it must cover the target Space. Organization-wide covers every current and future Space; Scoped access covers selected Spaces. Only me → Every Space is still personal, not organization-wide sharing.
See Managing Secrets for applicability, personal-secret limitations, and installation settings. Credentials managed by an MCP connection may follow that connection’s authentication flow; the steps above are for separately created, generic secrets.

​
Validate in a Fresh Session

After changing the configuration, access grants, or secret settings, start a new session in the target Space with the MCP server attached, using the intended recipient’s account. Test a harmless read-only tool call. An existing session may retain its earlier configuration or credentials, so it is not a reliable sharing test. Never print a secret value to verify access.

​
Pinning to an Expert

To make a registry server available inside a specific Expert, attach it from the Tools section of the Expert editor. The MCP server selector lists every server in the registry that the Expert can see — pick the ones you want and save. Pinned servers launch automatically with each session created from that Expert.

​
See Also

  • Skills — extend Experts with reusable knowledge packages using the agentskills.io specification
  • Understanding Files — the persistent storage layer that backs Skills and other Expert outputs