MCP.so
ログイン

Firma.dev Cheap E-Signature API MCP Server認証済み注目

@Firma-esign

基本情報

トランスポート

Streamable HTTP

認証方式

不要

カテゴリ

開発者ツール

作者

Firma-esign

投稿者

Monika Jain

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

接続情報

https://docs.firma.dev/mcp

セットアップ

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

Firma.dev Cheap E-Signature API MCP Server のツール

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, awk, 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.40.04/openapi-v01.40.04.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `/openapi/api-reference/v01.40.04/openapi-v01.40.04.json`, `/openapi/api-reference/v01.40.04/openapi-v01.40.04.fr.json`, `/openapi/api-reference/v01.40.04/openapi-v01.40.04.es.json`, `/openapi/api-reference/v01.40.02/openapi-v01.40.02.json`, `/openapi/api-reference/v01.40.02/openapi-v01.40.02.fr.json`, `/openapi/api-reference/v01.40.02/openapi-v01.40.02.es.json`, `/openapi/api-reference/v01.40.01/openapi-v01.40.01.json`, `/openapi/api-reference/v01.40.01/openapi-v01.40.01.fr.json`, `/openapi/api-reference/v01.40.01/openapi-v01.40.01.es.json`, `/openapi/api-reference/v01.40.00/openapi-v01.40.00.json`, `/openapi/api-reference/v01.40.00/openapi-v01.40.00.fr.json`, `/openapi/api-reference/v01.40.00/openapi-v01.40.00.es.json`, `/openapi/api-reference/v01.39.01/openapi-v01.39.01.json`, `/openapi/api-reference/v01.39.01/openapi-v01.39.01.fr.json`, `/openapi/api-reference/v01.39.01/openapi-v01.39.01.es.json`, `/openapi/api-reference/v01.39.00/openapi-v01.39.00.json`, `/openapi/api-reference/v01.39.00/openapi-v01.39.00.fr.json`, `/openapi/api-reference/v01.39.00/openapi-v01.39.00.es.json`, `/openapi/api-reference/v01.38.00/openapi-v01.38.00.fr.json`, `/openapi/api-reference/v01.38.00/openapi-v01.38.00.es.json`, `/openapi/api-reference/v01.37.00/openapi-v01.37.00.fr.json`, `/openapi/api-reference/v01.37.00/openapi-v01.37.00.es.json`, `/openapi/api-reference/v01.36.00/openapi-v01.36.00.fr.json`, `/openapi/api-reference/v01.36.00/openapi-v01.36.00.es.json`, `/openapi/api-reference/v01.35.00/openapi-v01.35…

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.

概要

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.

よくある質問

1

Firma.dev Cheap E-Signature API のリモート MCP サーバーとは何ですか?

Firma.dev Cheap E-Signature API のリモート MCP サーバーは、https://docs.firma.dev/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

Firma.dev Cheap E-Signature API の MCP サーバーにはどう接続しますか?

エンドポイント https://docs.firma.dev/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

Firma.dev Cheap E-Signature API の MCP サーバーは認証が必要ですか?

いいえ。Firma.dev Cheap E-Signature API の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。

4

Firma.dev Cheap E-Signature API の MCP サーバーはどのトランスポートを使用しますか?

Firma.dev Cheap E-Signature API は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント