본문 내용으로 건너뛰기

MCP

clepit의 MCP 표면은 에이전트가 워크스페이스와 페이지를 읽고 쓰도록 합니다. Bearer 전용이며, Origin 헤더를 가진 요청은 거부됩니다.

HostServes
https://api.clepit.com

mcp

POST/mcphttps://api.clepit.com

Invoke an MCP method

JSON-RPC 2.0 over HTTP. Every request needs Mcp-Protocol-Version: 2026-07-28.

Auth bearerAuth

Parameters

NameInTypeDescription
Mcp-Protocol-Version requiredheaderstringMust be 2026-07-28

Body

JSON
{
  "id": "integer",
  "jsonrpc": "2.0",
  "method": "server/discover | 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":{}}'

Protocol revision

Revision 2026-07-28. No session, no initialize handshake. A mismatched Mcp-Protocol-Version is rejected with JSON-RPC error -32020.

Browsers are not a supported client

The allowed-origins list is deliberately empty, so any request carrying an 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

Bash
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"}'