Documentation MCP server for Sorsa API (https://api.sorsa.io), an independent read-only API for public X/Twitter data. Lets AI assistants search and retrieve the public API documentation, endpoint guides and integration examples. This connector provides documentation, not live X/Twitter data. Documentation: https://docs.sorsa.io.
Scored across 3 tools
The three tools have largely distinct roles: search for broad/conceptual lookups, the filesystem query tool for exact regex, structural exploration, and full-page reads, and submit_feedback for reporting issues. There is inherent overlap since both search and the filesystem tool can surface documentation, but the descriptions explicitly delineate when to use each, keeping misselection low.
All names are verb-led and snake_case, which is readable, but the structure is uneven: two tools carry a verbose '_sorsa_developer_platform' suffix while submit_feedback does not, and the distinguishing verb_noun portions (query_docs_filesystem vs search) vary in granularity. Conventions are mixed enough to feel unpolished though not confusing.
Three tools is thin for a documentation server, though the filesystem tool is effectively a mega-tool that subsumes many read/search/explore operations. The set is borderline minimal rather than clearly well-scoped, with search and read being the only real capabilities plus feedback.
Search, page reading (via cat/head on the virtual filesystem), structural discovery (tree/ls), and feedback collectively cover the core documentation lifecycle. A dedicated list/get-page tool is absent, but the filesystem tool provides workarounds, leaving only minor gaps.
Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains ONLY the Sorsa Developer Platform 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/https://api.sorsa.io/v3/swagger.json' | jq '.paths | keys' — list OpenAPI endpoints
OpenAPI specs for this site are mounted at: '/openapi/https://api.sorsa.io/v3/swagger.json', /openapi/openapi-pt-BR.json, /openapi/openapi-es.json, /openapi/openapi-zh-Hans.json, /openapi/openapi-ja.json, '/openapi/document(1).json', /openapi/v3/openapi.json, /openapi/v2/openapi.json. 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.
Inputs: command (required).
Search across the Sorsa Developer Platform knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Sorsa Developer Platform, 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).
Inputs: query (required), language.
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.
Inputs: path (required), feedback (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.