API Reference
Zephex exposes one hosted MCP endpoint over HTTP. Every client sends JSON-RPC 2.0 requests to the same URL with Bearer token authentication.
| Property | Value |
|---|---|
| URL | https://zephex.dev/mcp |
| Method | POST |
| Transport | Streamable HTTP (JSON-RPC 2.0) |
| Auth | Authorization: Bearer YOUR_API_KEY |
| Content-Type | application/json |
AUTHENTICATION
Every request must include the Authorization header. Keys are created in the dashboard and are hashed server-side. Zephex does not store plaintext keys.
headers.txt
Authorization: Bearer zph_your_key_hereREQUEST FORMAT
Send JSON-RPC 2.0 with an id, a method, and method-specific params.
request.json
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_project_context", "arguments": { "path": "/path/to/repo" } }}METHODS
tools/list
Returns the available hosted tools and their input schemas so clients can inspect the tool surface before calling anything.
tools/call
Calls a named tool with its arguments and returns MCP content blocks in the result.
RESPONSES
response.json
{ "jsonrpc": "2.0", "id": 1, "result": { "content": [ { "type": "text", "text": "..." } ] }}| Code | Meaning |
|---|---|
| 401 | Invalid or missing API key. |
| 429 | Rate limit exceeded for your plan. |
| 400 | Malformed JSON-RPC request. |
| 500 | Internal server error. Report persistent failures. |
RATE LIMITS
| Plan | Requests/month | Backends |
|---|---|---|
| Free | 300 | 3 |
| Pro | 3,000 | 10 |
| Max | 10,000 | 20 |
Rate limit headers are returned on every response.
rate-limit-headers.txt
X-RateLimit-Limit: 300X-RateLimit-Remaining: 247X-RateLimit-Reset: 1714521600