MCP.so
Sign In

Firma.dev Cheap E-Signature API MCP ServerVerifiedFeatured

@Firma-esign

Basic information

Transport

Streamable HTTP

Authentication

None

Last updated

Category

Developer Tools

Author

Firma-esign

Submitted by

Monika Jain

About Firma.dev Cheap E-Signature API MCP Server

Firma.dev Cheap E-Signature API is a remote MCP server available at https://docs.firma.dev.

#API#E-signature#SAAS#Developer Friendly

Connection details

https://docs.firma.dev/mcp

Setup

claude mcp add firma-dev --transport http https://docs.firma.dev/mcp

Firma.dev Cheap E-Signature API MCP Server tools

3

Search across the Firma knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Firma, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Firma documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat /openapi/api-reference/v01.43.00/openapi-v01.43.00.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted under `/openapi`; run `find /openapi -type f` to list them. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Overview

The Firma.dev Docs MCP server gives AI assistants direct access to the Firma.dev documentation, so answers and generated code come from the current docs rather than guesswork.

Firma.dev is an e-signature API priced at €0.049 (~5¢ USD) per envelope, with no monthly minimums or per-seat fees.

Tools:

  • search_firma: Searches the full knowledge base, including API references, guides, and code examples.
  • query_docs_filesystem_firma: Runs read-only queries against the documentation pages and OpenAPI specs, useful for pulling exact endpoint schemas and request formats.
  • submit_feedback: Reports docs pages that are incorrect, outdated, or unclear to the Firma.dev docs team.

Typical workflows:

  • Generating code to create and send signing requests
  • Looking up endpoint parameters, request bodies, and webhook event payloads
  • Setting up embedded template and signing editors in your own app
  • Configuring workspaces, custom email domains, and webhooks
  • Checking the API changelog for recent changes

The server is read-only, requires no authentication, and only accesses published Firma.dev documentation. To act on live account data (templates, signing requests, workspaces), use the Firma.dev Data MCP at https://mcp.firma.dev/mcp.

Frequently asked questions

1

What is the Firma.dev Cheap E-Signature API remote MCP server?

The Firma.dev Cheap E-Signature API remote MCP server is a hosted Model Context Protocol endpoint at https://docs.firma.dev/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Firma.dev Cheap E-Signature API MCP server?

Add the endpoint https://docs.firma.dev/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Firma.dev Cheap E-Signature API MCP server require authentication?

No. Firma.dev Cheap E-Signature API's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the Firma.dev Cheap E-Signature API MCP server use?

Firma.dev Cheap E-Signature API exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments