Skip to main content

Context Sources

MCP Servers

Model Context Protocol (MCP) servers give Assistant tools for services your team already uses. After you connect a server, Assistant can read from that service and make changes there.

Nomic limits each marketplace server to an approved set of tools. Each server page shows which tools run directly and which require approval.

note

The MCPs pages are available when MCP tools are enabled for your account. If you do not see them, contact your Nomic administrator.

Add an MCP server​

Open Settings → MCPs. The page shows servers your organization has made available and servers already installed for you.

  1. Select a server. If it is not already on your list, select Add MCP.
  2. Select Login or Connect, if shown, and finish the service's sign-in flow.
  3. In Assistant, open Integrations/Tools → MCPs and turn on the server for that conversation.

An administrator can install a server by default, but cannot sign in on your behalf. Tools run with your account and the access that service grants to you.

Google is reviewing Nomic's production MCP app. Until approval, contact support@nomic.ai to whitelist your account before signing in to Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, or Google Slides.

Use MCP tools in Assistant​

Installing and signing in makes a server available to Assistant. MCPs you add from the marketplace appear under User. MCPs your organization installs by default appear under Organization, even before you sign in.

Assistant can also ask to connect or enable a server when a task needs it. Select Connect & continue or Enable & continue to resume the conversation with that server, or Continue without it.

When a tool needs approval, choose Allow once, Decline, or Always allow.

Manage a connection​

Select an installed server in Settings → MCPs to manage it.

  • Reconnect required means the saved authorization is no longer valid. Select Reconnect and complete sign-in again.
  • Log out or Disconnect removes your saved credentials.
  • Remove drops the server from your list. You can add an optional marketplace server again from the catalog. For a server installed by default, removing it opts you out until you add it back.

Removing an MCP server does not delete or change data in the connected service. You can also revoke Nomic from the service's own account or security settings.

Add a custom server​

Select Custom MCP in Settings → MCPs to connect a remote server that is not in the marketplace.

  1. Enter a name and the server's HTTPS URL.
  2. Add any required request headers. Nomic encrypts header values and does not show them again after you save.
  3. Select Test connection.
  4. Select Add MCP.

You can switch between Form and JSON while configuring the same server. Nomic supports remote HTTPS MCP servers that use OAuth or request headers. Local command or stdio servers are not supported.

Each member can add up to 25 custom servers. A JSON definition can contain one server, with up to 32 request headers. Personal custom OAuth servers must support dynamic client registration.

Only connect servers you trust. A custom server controls its tool descriptions and receives the information sent in its tool calls. All custom-server tools require approval.

Use the marketplace entries for Google Workspace, Smartsheet, Autodesk Forma, and Outlook. Their servers cannot be added through Custom MCP.

Manage organization MCP servers​

Organization administrators control the catalog in Admin → MCPs. These controls decide what members can install; they do not grant members access inside a connected service.

Set marketplace visibility​

Select a server and use the Visibility controls:

  • In the marketplace lets members find and add the server from Settings → MCPs.
  • Installed by default adds it to every member's list. Each member must still sign in when the server uses personal credentials.

Hiding a server removes it from members' MCP lists, including members who previously connected it. Showing it again restores availability, but a member may need to reconnect.

Some marketplace servers require an organization integration. Members see Requires the … integration and cannot add the server. Organization administrators can select Set up integration to open setup.

Add a shared custom server​

Select Add custom MCP in Admin → MCPs to define a server for the organization. Configure its URL and headers, test the connection, and choose whether it is available in the marketplace or installed by default.

For a server that requires a pre-registered OAuth application, add its OAuth client ID and secret. Register the callback URL shown by the server setup with the OAuth provider. OAuth client credentials and request headers cannot be used together. Nomic encrypts client secrets and saved header values.

The administrator who creates a shared custom server owns its definition. Other administrators can change its visibility or delete it, but cannot change its URL or credentials. Deleting it removes the server and members' saved credentials for it.

Marketplace servers​

Marketplace servers use individual sign-in. Assistant can reach only the data the signed-in member can access. Each page lists the server's tools, setup requirements, and example requests.

ServerUse it to
Autodesk FormaWork with issues, RFIs, submittals, and assets on imported projects.
Outlook MailSearch Microsoft 365 mail and prepare drafts.
Outlook CalendarCheck availability and manage Microsoft 365 meetings.
SmartsheetWork with schedules, registers, reports, and dashboards.
GmailSearch email and prepare drafts.
Google CalendarCheck availability and manage meetings.
Google DriveFind and read files that are not in a Nomic project.
Google DocsRead and edit documents.
Google SheetsAnalyze and update trackers, logs, and schedules.
Google SlidesRead and update presentations.
LinearFind, report on, and update issues, projects, and status updates.