Intro
Base URL¶
Authentication¶
Authentication methods vary by endpoint:
MCP Endpoint (/mcp) and REST API (e.g. /tools/call):
- OAuth2 (recomendado cuando el cliente lo soporte): el servidor obtiene tu identidad del token de acceso. Discovery: /.well-known/oauth-authorization-server.
- MCP Token:
- Recomendado: header Authorization: Bearer mcp_xxxxx o header x-mcp-token: mcp_xxxxx
- No recomendado: ?token=mcp_xxxxx en la URL (riesgo en logs/referrers)
Protected Endpoints (like /api/owner-ids/me, /api/user-preferences):
The system accepts authentication tokens in multiple ways (checked in order):
1. Authorization Header: Authorization: Bearer <token>
2. Cookie: auth_token cookie (set automatically after login)
3. Query Parameter: ?token=<token>
Main Endpoints¶
Health Check¶
Verifies the service status.
Endpoint: GET /health
Parameters: None
Response:
Example:
List Tools¶
Gets all available MCP tools.
Endpoint: GET /tools
Parameters: None
Response:
{
"tools": [
{
"name": "create_collection",
"description": "Create a new collection",
"inputSchema": { ... }
}
]
}
Example:
Call Tool¶
Executes a specific MCP tool.
Endpoint: POST /tools/call
Authentication: MCP token (e.g. Authorization: Bearer mcp_xxxxx) or OAuth2.
Body:
Response:
Example with MCP Token (Bearer, recommended):
curl -X POST "https://akashic-mcp.com/tools/call" \
-H "Authorization: Bearer mcp_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "list_collections",
"arguments": {}
}'
Nota: Los tokens se pueden crear y gestionar en /api/mcp-tokens. Para mayor seguridad usa OAuth2 cuando el cliente lo soporte.
Related Documentation¶
- API Reference - Complete API reference
- Getting Started - Quick start guide