Skip to main content

Context Sources

MCP Servers

Model Context Protocol (MCP) servers give the Nomic agent tools for services your team already uses. After you connect a server, it 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.

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 a conversation, open Integrations/Tools → MCPs on the input bar 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, signing in to Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, or Google Slides shows an unverified app warning. Select Advanced, then the Go to … (unsafe) link, and approve the requested permissions.

Use MCP tools in a conversation​

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

The Nomic agent 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, the approval card shows the tool's arguments and a countdown. Choose Always allow this tool, Allow this time, or Don't allow. If the countdown ends before you respond, the request expires. Always allow this tool is not offered when your administrator requires approval for that tool on every call.

Set tool permissions​

Each tool has one of three permissions:

  • Always allow runs the tool without asking.
  • Needs approval asks you before every call.
  • Blocked never runs the tool.

Open an installed server from Settings → MCPs and find Tool permissions in its detail view. Tools are grouped as Read only tools and Write/delete tools. A custom server's tools appear in a single Tools group. Set one tool with its toggle, or set a whole group with the menu in the group header. Tools that only read data start as Always allow; tools that can change data start as Needs approval.

Your administrator can set a different starting permission for your organization. When an administrator locks a tool, it shows Set by admin. You can make a locked tool stricter, for example from Needs approval to Blocked, but you cannot loosen it. Nomic can also block tools outright, and these cannot be changed.

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. By default, custom-server tools require approval, and you can change each tool's permission in Tool permissions.

Use the marketplace entries for Google Workspace, Smartsheet, Dropbox, Autodesk Forma, Trimble ProjectSight, Procore, Outlook, and Microsoft Teams. 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, such as Autodesk Forma, Trimble ProjectSight, and Procore, run on an organization integration. Until an administrator sets up that integration, members do not see the server. In Admin → MCPs it shows Requires integration, and its visibility cannot be turned on. Select the server, then select Set up under Integration.

Set tool permissions for your organization​

Select a server in Admin → MCPs and use Tool permissions to choose the starting permission members get for each tool: Always allow, Needs approval, or Blocked. Set one tool, or set a whole Read only tools or Write/delete tools group at once. For a custom server, a single All tools setting covers every tool, including tools the server adds later. Use Reset all to default to clear your changes.

Changing a permission also locks it, so members can only make it stricter. Unlock it with the lock button to let members loosen it again. Always allow cannot be locked because it is the loosest choice. Members see locked tools labeled Set by admin, and approval cards for a tool that is locked to Needs approval do not offer Always allow this tool.

Permissions control whether Nomic asks before using a tool. They do not change what a member can access in the connected service.

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. Nomic 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.
Microsoft TeamsCatch up on chats, channels, and meeting transcripts, and post updates.
SmartsheetWork with schedules, registers, reports, and dashboards.
DropboxFind, read, organize, and share Dropbox files.
MiroRead boards and comments, and add diagrams, documents, and tables.
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.
ProcoreWork with RFIs, submittals, punch items, and observations on synced projects.
Trimble ProjectSightWork with issues, RFIs, submittals, and daily reports on imported projects.