MCP overview
Exayard exposes the Model Context Protocol at https://api.exayard.com/mcp. Streamable HTTP transport, OAuth-protected, 124 tools. The protocol version is MCP 2025-06-18.
Capabilities
Advertised at /.well-known/mcp.json:
tools— 124 tools across projects, files, pages, assessments, products, vendors, estimates, bids, webhooks, etc.prompts— four shipped playbooks for common multi-step workflows.resources/sampling— not yet implemented.
Auth
Two bearer-token paths:
- API key — pass the same
sk_live_...you'd use on the REST API. - OAuth — discover the authorization server at /.well-known/oauth-protected-resource. DCR-registered clients get their own
client_id— see Dynamic Client Registration.
401 responses carry WWW-Authenticate: Bearer realm="Exayard MCP", resource_metadata="..." so MCP clients can negotiate without hard-coded config.
Tool annotations
Every tool declares readOnlyHint, destructiveHint, and idempotentHint. Clients use these to decide auto-approval policy. Prefixes map to the intent:
| Prefix | readOnly | destructive | idempotent |
|----------------|----------|-------------|------------|
| get_/list_/search_/find_ | ✓ | ✗ | ✓ |
| update_/set_/patch_/rename_/move_ | ✗ | ✗ | ✓ |
| archive_/remove_/cancel_ | ✗ | ✓ | ✓ |
| create_/add_/batch_/run_ | ✗ | ✗ | ✗ |
Token budget
Tool responses larger than 60,000 characters are auto-truncated. The response carries _truncated: true + a _hint string explaining how to paginate.
Structured content
Tools return both content (text fallback) and structuredContent (JSON object, per MCP 2025-06-18). Agents branch on structuredContent fields directly.