Server facts
sushimcp MCP Server
Project
- Author
- maverickg59
- Repository
- github.com/maverickg59/sushimcp
- Website
- sushimcp.com
- License
- AGPL-3.0
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 9
- Last commit
- Data as of
Tags
- llms full
- llms mini
- llms txt
- llmstxt
- mcp
- mcp server
- tools
Overview
Documentation lookup and API reference retrieval are the core workflows in SushiMCP, which delivers context to AI IDEs through MCP. Developers can configure named sources for llms.txt documentation and OpenAPI specifications. The documentation workflow starts with list_llms_txt_sources to discover available source URLs, followed by fetch_llms_txt to retrieve selected content. That fetch tool accepts multiple URLs, supporting retrieval from more than one documentation source. When an llms.txt file acts as an index rather than containing the needed material, its references can lead to additional llms.txt files.
API specifications follow a separate discovery-and-fetch path: list_openapi_spec_sources exposes the available specification URLs, and fetch_openapi_spec retrieves content from selected addresses. The documentation tool guidance favors llms.txt initially, with llms-full.txt or llms-mini.txt as alternatives when the initial material is insufficient. Together, these tools serve developers who want documentation and API descriptions available to their coding assistants. SushiMCP runs on Node and uses stdio transport.
sushimcp setup notes
- sushimcp records stdio only; confirm a network transport upstream before planning remote access.