MCP endpoint (Streamable HTTP)
SignStack's Model Context Protocol server for AI assistants. The body is a JSON-RPC 2.0 request per the MCP specification (revision 2026-07-28 with per-request MCP-Protocol-Version, Mcp-Method and Mcp-Name headers; 2025-era clients that open with initialize are served too). Authenticate with a connected-app access token issued for resource=<api>/mcp; REST tokens, API keys and session tokens are refused. Tools that operate agreements: get_connection, list_blueprints, get_blueprint_inputs, find_workflows, get_workflow, get_workflow_events, create_workflow, void_workflow, send_reminder, get_signed_document_link. Tools that author them with the client's own model: get_authoring_guide, list_resources, get_resource, validate_resources, check_render, save_drafts, list_scenarios, save_scenario, preview_document, get_preview, plan_publish, publish_resources; the authoring guide is also served as signstack:// resources with an author_agreement prompt. Tools that start from the library and hand out public forms: search_library, get_listing, copy_listing, create_shareable_link, list_shareable_links, update_shareable_link; create_workflow also takes a listing. The full catalogue is 28 tools. SignStack makes no AI-model call for a connection. The list a client sees is filtered to the scopes its connection holds. GET and DELETE answer 405 (401 without a valid token). See the guide Connecting AI Assistants (MCP).
Body
Responses
- application/json
- 400
A JSON-RPC batch carrying more than 20 messages. Each message in a batch counts against the connection's rate limit.
- 401
No or invalid token.
WWW-Authenticate: Bearer resource_metadata="<api>/.well-known/oauth-protected-resource/mcp", scope="…"tells the client where to authorize. - 403
Origin not allowed, or the connection lacks a scope the tool needs (
WWW-Authenticate: Bearer error="insufficient_scope", scope="…"). - 429
Rate limit for this connection exceeded;
Retry-Aftersays when to retry.
curl https://api.signstack.ai/mcp \
--request POST \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_workflow",
"arguments": {
"workflow_id": "wf_01jv8m7qfj6xj9gkz7a4s2h8e"
},
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28"
}
}
}'
{}