Skip to main content
POST
Create an MCP server

Side effects

When an MCP server is successfully created:
  1. Tool sync - Basedash connects to the MCP server and syncs its tools
  2. OAuth bootstrap - If the server advertises OAuth, the response includes an authorization URL
  3. Trial activation - If the organization has never been on a trial, a trial period is automatically started

Authorizations

Authorization
string
header
required

API key authentication using Bearer token format: Bearer <basedash_api_key>

Path Parameters

orgId
string
required

Organization ID

Body

application/json
displayName
string
required

Display name for the MCP server

Required string length: 1 - 120
serverUrl
string
required

MCP server URL

Required string length: 1 - 2000
headers
object[]

Static headers to use when connecting to the MCP server

everyoneInOrganizationCanAccess
boolean
default:true

Whether every member in the organization can use this MCP server

Response

MCP server created successfully

data
object
required