sign_api_delete
Sends a DELETE request to a freee Sign API path.
LABSCO SUMMARY
Sending a document for signature starts from a file path, not a Base64 blob.
The upload tool exists for a specific failure: passing Base64 in a request body breaks once the file is large, so document creation gets its own call with the fields that matter — folder, signers, approval skip. Everything past documents is unmodelled, which cuts both ways: nothing in the API is out of reach, and you want the API reference in context because the five verb tools take a raw path.
What it is
A thin client for the freee Sign API: an OAuth handshake, a file-upload path for creating documents, and five verb-shaped passthrough calls for everything the server does not model. It is the electronic-contract half of freee's MCP package, which also carries servers for the accounting, HR, invoicing, project, sales, IT-management and contractor APIs.
What you get
- OAuth handled in three tools: start the flow once, check the current authentication state, clear the stored credentials
- Document creation straight from a local file path, posting to /v1/documents/uploads or /v1/pdf_documents, with folder, title, signer count and an approval-skip option
- The rest of the API by path — GET, POST, PUT, PATCH and DELETE, each taking a path, a query and where relevant a body
- Requests validated against the OpenAPI schema and the access token attached before they go out
- A report of the running server's own details, for confirming which build is answering
Requirements
A freee account that can complete the freee Sign OAuth flow, and the documents you want to send as local files. freee Sign is not on freee's remote MCP server yet, so this one runs on your machine: Node.js, an application registered in the freee app store with the callback URL http://127.0.0.1:54321/callback, and npx --package=freee-mcp -- freee-sign-mcp configure, whose wizard stores the credentials and runs the OAuth sign-in. freee publishes a companion Agent Skill carrying the API reference, which is what keeps the raw-path calls from being guesswork. Apache-2.0 licensed.
Setup effort
One command plus credentials — npx --package=freee-mcp -- freee-sign-mcp configure, then supply credentials
USE CASES
01
Getting connected the first time
Run the OAuth flow once, then check the authentication state before the agent tries anything else.
02
Sending a contract for signature
Create the document from the PDF on disk, with its folder, title and signer count set on the same call.
03
Checking where a document has got to
Read the document and its status by path, rather than opening the freee Sign web app.
04
Doing something the upload tool does not cover
Call the endpoint directly with the verb it needs — the path, query and body are yours to specify.
05
Handing the machine back
Clear the stored credentials so the next person's session does not inherit yours.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
sign_api_get
Sends a GET request to a freee Sign API path.
sign_api_patch
Sends a PATCH request to a freee Sign API path.
sign_api_post
Sends a POST request to a freee Sign API path; for creating a document from a file, use sign_file_upload rather than a Base64 body.
sign_api_put
Sends a PUT request to a freee Sign API path.
sign_auth_status
Reports the current freee Sign authentication state.
sign_authenticate
Starts the freee Sign OAuth flow, needed only the first time.
sign_clear_auth
Clears the stored freee Sign credentials.
sign_file_upload
Creates a freee Sign document from a local file, posting to /v1/documents/uploads or /v1/pdf_documents; use this rather than a Base64 body, which fails on large files.
sign_server_info
Returns details about the freee-sign-mcp server itself.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. These 10 are the sign_* tools of the freee-sign-mcp contract server. The documentation lists 23: 9 management and 6 API tools on the main freee-mcp server, plus 8 sign tools.
Requires
- npx on PATH
- A freee app created in the freee App Store (https://app.secure.freee.co.jp/developers) with the callback URL http://127.0.0.1:54321/callback and the permissions you need
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx --package=freee-mcp -- freee-sign-mcp configureMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"freee-sign-mcp": {
"command": "npx",
"args": [
"--package=freee-mcp",
"--",
"freee-sign-mcp"
]
}
}
}Claude Code — plugin
CLAUDE CODE — PLUGIN · TERMINAL
claude plugin marketplace add freee/freee-mcp
claude plugin install freee-mcp@freee-mcp-marketplaceCodex — plugin
CODEX — PLUGIN · TERMINAL
codex plugin marketplace add freee/freee-mcpThen start Codex, open the plugin list with the /plugins slash command, select freee-mcp and run Install plugin.
