Platform MCP

Platform MCP is an MCP server exposed by A²D that lets AI agents perform UI-like operations — CRUD for MCP Server specifications, Agent Card specifications, Tests, Suites, and Exploratory Sessions — via standard MCP tools.

Overview

Use Platform MCP when you want AI assistants (e.g., in Cursor, Claude, or custom agents) to design specifications, run tests, manage exploratory sessions, or fetch specs without using the A²D UI. API keys are scoped per organization.

Key capabilities:

• List, search, design, update, and delete MCP Server and Agent Card specifications
• Add tools, resources, and prompts to MCP Server specifications; add skills to Agent Card specifications
• Duplicate and import specifications from JSON
• Retrieve server/card specs as JSON (Exchange-published shape)
• Manage test cases, suites, and run tests
• Create and manage exploratory sessions (assets, invites, activation)

Endpoint and Transport

Replace {baseUrl} with your A²D deployment URL (e.g., https://ma2d.vercel.app).

Authentication

Authentication is required. API keys are organization-scoped.

Headers (use one):

• Authorization: Bearer <your-api-key>
• X-API-Key: <your-api-key>

Warning: API keys are sensitive. Store them securely and never commit them to source control.

Managing API Keys

1. Go to Settings > Platform MCP
2. Copy the endpoint URL for your environment
3. Click Generate API Key and enter a name
4. Copy the raw key immediately — it is shown only once
5. Revoke keys you no longer need

Tool Categories

Platform MCP exposes 55+ tools across eight categories. All MCP Server and Agent Card tools operate on specifications — design documents that define servers and cards.

MCP Server Specifications

MCP Server Child Entities (Tools, Resources, Prompts)

Add, update, or remove tools, resources, and prompts within an MCP Server specification.

Agent Card Specifications

Agent Card Skills

Duplicate and Import

Tests

Suites

Exploratory Sessions

Designing Complete Specifications

When you create a new MCP Server or Agent Card with design_mcp_server or design_agent_card, the entity starts empty. Use the child-entity tools to build it:

MCP Server workflow:

1. design_mcp_server — create the server
2. add_mcp_tool, add_mcp_resource, add_mcp_prompt — add tools, resources, and prompts
3. get_mcp_server_spec — retrieve the full spec as JSON when ready

Agent Card workflow:

1. design_agent_card — create the card
2. add_agent_skill — add skills
3. get_agent_card_spec — retrieve the full spec as JSON when ready

Alternatively, use import_mcp_server or import_agent_card with a design spec JSON object to create a fully populated specification in one step.

Example: Listing MCP Servers

After connecting with a valid API key, call tools/call with the tool name and arguments:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_mcp_servers",
    "arguments": {}
  }
}

For detailed request/response formats, see API Reference.

Next Steps

• API Reference - Platform MCP Endpoint
• Settings & Organization — API key management
• Test Lab — Execution, Exploratory sessions, Test Runs
• Testing Framework (A2TF) — Test design and execution

Platform MCP enables AI agents to manage your A²D assets programmatically.