Skip to main content
Glama

create_mcp_server

Creates and registers an MCP server under an existing integration, returning the new ID and slug so you can configure it with capabilities or access tools.

Instructions

Create an MCP server under an existing integration. Registers the server and returns the new id and slug; use list_mcp_integrations first to find the parent integration, then capabilities or access tools to configure it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "mcp_integration_id": "<mcp_integration_id>"
    },
    "name": "create_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name for the MCP server
slugNoCustom slug. Auto-generated if omitted
tagsNoKey-value tags. Replaces existing tags; pass null to clear. Keys allow letters, numbers, underscores, and hyphens
descriptionNoDescription of the MCP server
workspace_idNoWorkspace ID or slug; required with an organisation admin API key
mcp_integration_idYesID or slug of the MCP integration this server belongs to

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.16.5
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Workspace ID or slug; required with an organisation admin API key",
      +  "type": "string"
      +}
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed1 schema field changedv0.16.4
    • addedInput schema / properties / tags
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "propertyNames": {
      +        "pattern": "^[a-zA-Z0-9_-]+$",
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Key-value tags. Replaces existing tags; pass null to clear. Keys allow letters, numbers, underscores, and hyphens"
      +}
  3. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Addedv1.0.1

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the mutation and safety profile is supplied structurally. The description adds that the server is registered and the new id and slug are returned, plus the follow-up configuration path, but since an output schema exists the return-value note is partly redundant and nothing is said about failure modes such as slug collisions or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler: the effect statement comes first, the prerequisite and follow-up workflow second. Every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter create tool with full schema coverage, an output schema, and existing annotations, the description supplies the missing workflow context (parent lookup, post-create configuration). It leaves out collision behavior and the admin-key requirement for workspace_id (that one is at least noted in the schema), which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, covering name, slug auto-generation, tags, description, workspace_id and mcp_integration_id, so the baseline is 3. The description adds only the lookup route for the parent integration via list_mcp_integrations and does not elaborate on any individual parameter's semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create an MCP server') and scopes it with 'under an existing integration', which separates it from the sibling create_mcp_integration. An agent can tell immediately which entity is being created and what the parent relationship is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes ordering: call list_mcp_integrations first to obtain the parent integration, then use capabilities or access tools afterwards to configure. It gives no when-not-to-use condition or comparison against update_mcp_server/upsert_guardrail_mcp_server, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools