Koskamo

Kamy MCP MCP server

The Kamy MCP server provides 59 tools for AI agents to handle document infrastructure, including rendering PDFs and other formats, performing PAdES-grade electronic signatures, extracting structured data from inbound documents, and verifying cryptographic seals. It allows agents to generate, sign, and audit documents without manual wiring of multiple vendors.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Kamy
MCP endpoint (Streamable HTTP)
https://mcp.kamy.dev/mcp
Vendor documentation

What you can do with it

  • Render PDFs, Word docs, and spreadsheets from templates
  • Apply PAdES electronic signatures to documents
  • Extract structured JSON data from uploaded PDFs
  • Verify cryptographic seals and audit trails of documents
Tools advertised by the last live check:
  • list_templates
  • get_template_schema
  • create_template
  • update_template
  • publish_template
  • rollback_template
  • list_template_versions
  • get_template_version
  • render_pdf
  • render_docx
  • render_pptx
  • render_xlsx
  • render_html
  • convert_document
  • merge_pdfs
  • split_pdf
  • edit_pdf
  • upload_file
  • get_upload
  • validate_payload
  • extract_document
  • ask_kamy
  • create_signature_request
  • create_envelope
  • list_signature_requests
  • get_signature_certificate
  • get_signature_request
  • get_envelope
  • remind_signature
  • bulk_signature_requests
  • preview_field_placement
  • list_signature_templates
  • get_signature_template
  • pki_sign_pdf
  • verify_pdf_signature
  • attest_artifact
  • verify_attestation
  • record_agent_action
  • get_provenance_chain
  • trace_record
  • trace_record_batch
  • trace_search
  • verify_mcp_server
  • scan_tool_description
  • get_started
  • get_account
  • list_renders
  • get_render
  • get_render_pages
  • extract_from_render
  • render_async
  • get_job
  • render_batch
  • create_schedule
  • list_schedules
  • delete_schedule
  • create_webhook
  • list_webhooks
  • test_webhook

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http kamy-mcp https://mcp.kamy.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add kamy-mcp --url https://mcp.kamy.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable kamy-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "kamy-mcp": {
      "url": "https://mcp.kamy.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "kamy-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.kamy.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start kamy-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "kamy-mcp": {
      "type": "http",
      "url": "https://mcp.kamy.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http kamy-mcp https://mcp.kamy.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "kamy-mcp": {
      "url": "https://mcp.kamy.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "kamy-mcp": {
      "serverUrl": "https://mcp.kamy.dev/mcp"
    }
  }
}

Do you run Kamy MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing