Managing MCP Access

This page is for workspace admins who assign and manage MCP access for their team. If you're a team member looking to connect an AI tool, see Getting Started with MCP.

Before you begin

Your workspace must have MCP. MCP is purchased separately from your Crunchbase subscription; any workspace can add it regardless of plan tier. Seats from your MCP purchase are assigned to individual team members.
You need admin privileges. Assigning MCP seats is available to workspace Owners and Admins.

You can see how many MCP seats your workspace has and how many are assigned in Team Settings → Team Members.

Inviting team members

MCP seats can only be assigned to members of your Crunchbase workspace. If the person isn't in your workspace yet:

Go to Settings → Team Members.
Click Invite Team Members and enter their email address.
The invitee receives an email and must accept the invitation to join your workspace.

Until they accept, they won't appear as assignable in your Team Members list. Once they've joined, continue below.

Assigning an MCP seat

Go to Settings → Team Members.
Find the team member in the list and click Manage next to their name.
Choose Assign MCP Seat.

The MCP Seat column updates to reflect the assignment. The team member can now connect any supported AI tool by signing in with their Crunchbase account; point them to Getting Started with MCP for setup.

An MCP seat controls whether a user can connect. MCP is purchased independently of your Crunchbase plan tier, so the two are managed separately: your MCP purchase determines how many seats you can assign.

Removing an MCP seat

Go to Settings → Team Members.
Click Manage next to the team member's name.
De-select Assign MCP Seat.

Pre-registered OAuth clients

Some AI tools require pre-registered OAuth credentials rather than connecting directly (see Pre-registered OAuth clients in Connecting AI Tools).

Registrations are set up by contacting your account team or support. Admins can view each client's Client ID and Client Secret under Settings → Integrations → MCP; the callback URL for each client is configured by Crunchbase and shown read-only.

These credentials identify the connecting application; each team member still signs in with their own account and needs their own MCP seat.

Frequently asked questions

Can multiple people share one MCP seat?
No. Seats are per user, and each connection is tied to the individual who signed in. For unattended or shared automation, contact your account team or support.

Does an MCP seat use up API quota?
No, your MCP and API quotas are separate.

A team member logs in to their AI tool of choice using Crunchbase, but the agent cannot access Crunchbase data.
They most likely don't have a seat assigned, or their seat was removed. Assign one following the steps above; the change takes effect immediately for new connections.