apidevelopermcp

Tools API and MCP

Planned unified gateway for Amen API keys, REST resources and MCP tools.

Amen’s target design publishes one product-owned tool registry through REST, MCP and a CLI without moving platform data into the product database.

Delivery status

/api/v1/* returns 501 AMEN_RESOURCE_GATEWAY_UNAVAILABLE.
/api/mcp and /api/mcp/:transport return 501 AMEN_MCP_GATEWAY_UNAVAILABLE.
Core API-key creation, rotation and revocation are already live.

Required architecture

One product-owned registry must describe every external capability:

type AmenTool = {
  name: string;
  description: string;
  inputSchema: object;
  requiredScopes: string[];
  execute(context: { workspaceId: string; userId: string }, input: unknown): Promise<unknown>;
};

REST and MCP adapters must resolve the API key or OAuth token through an Amen service, derive workspaceId from the credential, validate the input once and call the same handler. They must not maintain separate tool lists.

Missing Amen service

The required external resource/MCP gateway is specified in MISSING-AMEN-SERVICES.md. Until it exists, the stable 501 response prevents a client from mistaking a planned example for a working Amen contract.