Context7

Context7 is a third-party MCP server that indexes the documentation of popular libraries and SaaS APIs and serves it to AI coding assistants on demand. SignatureAPI is indexed there, so any MCP-aware coding tool can pull accurate, current documentation for the API directly into its prompt.

What Context7 gives you

When your coding assistant has Context7 wired up, you can append use context7 to any prompt and the assistant will:

1. Resolve “SignatureAPI” to the indexed library (/websites/signatureapi).
2. Fetch a focused slice of the documentation relevant to your question.
3. Use that content to ground the code it generates.

The result: fewer hallucinated field names, fewer outdated endpoints, and code that lines up with the current API spec instead of whatever the model saw in training.

Adding Context7 to your assistant

Context7 ships as a standard MCP server. The setup is identical to adding any other MCP connection.

Cursor

Add Context7 to your Cursor MCP configuration:

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http context7 https://mcp.context7.com/mcp

Claude Desktop, Windsurf, VS Code, JetBrains

See the Context7 installation guide for the configuration block specific to your editor. The URL is always https://mcp.context7.com/mcp.

Using it with SignatureAPI

Once Context7 is connected, mention SignatureAPI in your prompt and ask the assistant to use Context7. A few examples:

Write a Node.js function that creates a SignatureAPI envelope with two signers in a fixed order. use context7

Show me how to embed a SignatureAPI signing ceremony in a React app using the @signatureapi/web SDK. use context7

What fields can I set on a Place in SignatureAPI? use context7

Context7 will resolve the library, pull the relevant snippets from the docs, and the assistant will write code grounded in the actual API.

Library identifier

Context7 identifies SignatureAPI as /websites/signatureapi. You can pass this id explicitly if your assistant exposes the underlying tool calls:

Tool	Argument
resolve-library-id	libraryName: "signatureapi"
get-library-docs	context7CompatibleLibraryID: "/websites/signatureapi"

Pairing with other context sources

Context7 and our own LLM indexes are complementary:

• Use Context7 when you want your editor to pull the latest docs in-context as you code, with no manual file copying.
• Use llms.txt / llms-full.txt when you want full control over what gets sent to the model — for example, embedding a snapshot in a system prompt.
• Use the SignatureAPI MCP server when the agent should not only learn about the API but actually act on it (create envelopes, manage signing).