Developer Tools
sufy.com
Provides access to Sufy documentation through search, listing, and content retrieval.
ENDPOINT 1
https://developer.sufy.com/mcp
MCP server metadata
- Name
- Sufy
- Version
- 1.0.0
Use tools/list to discover available tools, then call search_sufy, list_docs_sufy, get_doc_content_sufy, or query_docs_filesystem_sufy to explore the Sufy documentation.
Known tools 4
search_sufySearch across the Sufy documentation to find relevant guides, API references, tutorials, and examples.
Inferred read-onlylist_docs_sufyList all indexed Sufy documentation pages with titles, routes, URLs, and descriptions.
Inferred read-onlyquery_docs_filesystem_sufyRun a read-only query against a virtual documentation filesystem rooted at /.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sufy]
url = "https://developer.sufy.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sufy": {
"type": "http",
"url": "https://developer.sufy.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sufy
Remote MCP URL: https://developer.sufy.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sufy": {
"url": "https://developer.sufy.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sufy": {
"type": "http",
"url": "https://developer.sufy.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sufy",
"transport": "streamable-http",
"url": "https://developer.sufy.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for sufy.com was fetched 2026-08-04T18:54:28.494Z and is being refreshed.
sufy.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.