Get Project Key Mcp Config

Returns authoritative MCP tool scoping config for server-side enforcement.

Called by the MCP server on session start to verify tool_profile, allowed_tools, and blocked_tools — preventing credential file tampering.

GET /project-keys/{project_key_id}/mcp-config

Get Project Key Mcp Config

cURL

curl --request GET \
  --url https://api.streamkap.com/project-keys/{project_key_id}/mcp-config \
  --header 'Authorization: Bearer <token>'

200

{
  "project_key_id": "<string>",
  "tenant_id": "<string>",
  "service_id": "<string>",
  "kafka_username": "<string>",
  "allowed_tools": [
    "<string>"
  ],
  "blocked_tools": [
    "<string>"
  ]
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

project_key_id · string · required

Response

200

application/json

Successful Response

Authoritative MCP tool scoping config for server-side enforcement.

Includes identity fields (tenant_id, service_id, kafka_username) so the MCP server can enrich audit logs with verified context without trusting the credential file.

project_key_id · string · required

tenant_id · string · required

service_id · string · required

kafka_username · string | null

tool_profile · enum<string> | null

Available options: full, read-only, agent-operator, infra-admin

allowed_tools · string[] | null

blocked_tools · string[] | null