REST API
MCP
Derived from the source of github.com/awee-ai/api/cmd/mcp.
Awee MCP API · v1.0.0 · 2 endpoints
Well Known
GET/.well-known/oauth-protected-resourcePublic
Serves the protected-resource metadata a client reads to find the authorization server that issues tokens for this resource
mcp.HTTPTransport.handleMetadata
Takes no parameters and no request body.
Responses
200 OKOK
200 OKOK
authorization_serversstring[]resourcestringrequiredRequest
No request body.
200 OK
{
"authorization_servers": [
"string"
],
"resource": "string"
}MCP
POST/mcpAuth
Validates the bearer, seeds it onto the context, and dispatches a single JSON-RPC request through the same server dispatch the stdio transport drives
A missing or invalid token is answered with 401 and a challenge that points the client at the protected-resource metadata.
mcp.HTTPTransport.handleRPC
Body
application/jsonrequiredidunknownjsonrpcstringrequiredmethodstringrequiredparamsunknownResponses
200 OKOK
200 OKOK
errorRPCErrorIs the error object of a failed JSON-RPC response.
errorRPCErrorcodeinteger (int64)requireddataunknownmessagestringrequiredidunknownjsonrpcstringrequiredresultunknown202 AcceptedAccepted
No response body.
401 Unauthorizedthe request could not be completed
401 Unauthorizedthe request could not be completed
errorstringrequiredDefaultthe request could not be completed
Defaultthe request could not be completed
errorstringrequiredRequest body
{
"id": null,
"jsonrpc": "string",
"method": "string",
"params": null
}200 OK
{
"error": {
"code": 0,
"data": null,
"message": "string"
},
"id": null,
"jsonrpc": "string",
"result": null
}