Sushi Tools
SushiMCP comes loaded with a set of tools designed to feed context to your AI IDE's. Not just any context, but up to date, accurate, context from the source documentation.
Available Tools
Roadmap
Tool Name | Identifier | Description | Status |
---|---|---|---|
List Sources | list_llms_txt_sources | Lists all llms.txt sources. | Complete |
List Resources | list_resources | Lists all resources. | Complete |
Fetch Source | fetch_llms_txt_source | Fetches a specific llms.txt. | Complete |
Fetch Open API Spec | fetch_openapi_spec | Fetches a specific OpenAPI spec. | Complete |
Git Ingest | git_ingest | Ingests a git repository into the MCP server. | WIP |
Pseudo llms.txt | pseudo_llms_txt | Scrape a docs site to build a pseudo llms.txt file. | Planned |
Find Source | find_llms_txt_source | Search for llms.txt by identifier. | Planned |
Search Stack Overflow | search_stackoverflow | Search Stack Overflow for answers. | Planned |
Best Practices
Best practices when requesting your AI agent to call SushiMCP tools:
- Carefully consider how you make requests for documentation. Base models sometimes fall into a loop when missing documentation is requested in a way that leads the model to believe the documentation should be available.
Ask SushiMCP for XYZ docs.
This approach is fine if you know the llms.txt source is available.
--vs--
Ask SushiMCP for any available documentation for Hono and Drizzle.
- Remember that some projects make
llms-full.txt
andllms-mini.txt
available alongside llms.txt - Some
llms.txt
are just a collection of links - request anllms-full.txt
orllms-mini.txt
if available - Request the appropriate level of documentation based on your needs
- Take into account the context window made available by your chosen model
- The
llms.txt
standard is relatively new so expect that many projects will not adhere
Tool Request
Have a tool idea you want added? Submit a request