MCP
clepit の MCP サーフェスにより、エージェントはワークスペースとページを読み書きできます。Bearer のみで、Origin ヘッダーを伴うリクエストは拒否されます。
| Host | Serves |
|---|---|
| https://api.clepit.com |
mcp
Invoke an MCP method
JSON-RPC 2.0 over HTTP. A request carries its revision in Mcp-Protocol-Version: 2026-07-28, or the 2025 revision a client agreed in its initialize handshake.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| Mcp-Protocol-Version | header | string | 2026-07-28, or the revision initialize answered; initialize itself carries none |
Body
{
"id": "integer",
"jsonrpc": "2.0",
"method": "server/discover | initialize | notifications/initialized | ping | tools/list | tools/call",
"params?": "object"
}Responses
200 A JSON-RPC 2.0 response object.
Try it
curl -X POST "https://api.clepit.com/mcp" \
-H "Authorization: Bearer $BEARER_AUTH" \
-H "Content-Type: application/json" \
-d '{"id":0,"jsonrpc":"2.0","method":"server/discover","params":{}}'const response = await fetch('https://api.clepit.com/mcp', {
method: 'POST',
headers: {
Authorization: `Bearer ${bearerAuth}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"id": 0,
"jsonrpc": "2.0",
"method": "server/discover",
"params": {}
}),
});
const data = await response.json();final response = await http.post(
Uri.parse('https://api.clepit.com/mcp'),
headers: {
'Authorization': 'Bearer $bearerAuth',
'Content-Type': 'application/json',
},
body: jsonEncode({"id":0,"jsonrpc":"2.0","method":"server/discover","params":{}}),
);response = requests.post(
"https://api.clepit.com/mcp",
headers={"Authorization": f"Bearer {bearer_auth}"},
json={"id":0,"jsonrpc":"2.0","method":"server/discover","params":{}},
)Protocol revision
This server targets revision 2026-07-28, where every request carries its own revision and there is no session. Clients that open with an initialize handshake are served too, on revisions 2025-11-25, 2025-06-18 and 2025-03-26: initialize answers the revision the client asked for, or 2025-11-25 when it asked for one the server does not serve, and no session is issued. A request naming a revision the server does not serve is rejected with JSON-RPC error -32022, which lists the revisions it does.
Browsers are not a supported client
Origin header is refused. This is a machine-to-machine surface; widening it is a security decision, not a configuration tweak.Discovery
GET /.well-known/oauth-protected-resource/mcp stays reachable with no token at all, it is how an unauthenticated client learns where to authenticate. Its resource is https://api.clepit.com/mcp, the address a client connects to.
すべてのツール、リソース、プロンプトは、サーバー自体から生成されたページに掲載されています:MCP ツール、MCP リソース、MCP プロンプト。
Listing the tools
curl -X POST "https://api.clepit.com/mcp" \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-H "Mcp-Protocol-Version: 2026-07-28" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'