innerloop--llms-txt — Innerloop MCP Resource

innerloop--llms-txt is one of 14 resources on the Innerloop MCP server. Connect the server and your client can attach it as context.

by client

How to attach innerloop--llms-txt from your client

• Claude Code Innerloop Resource/innerloop--llms-txt run in your project directory
• Claude Desktop Innerloop Resource/innerloop--llms-txt ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Innerloop Resource/innerloop--llms-txt ~/.cursor/mcp.json
• VS Code Innerloop Resource/innerloop--llms-txt .vscode/mcp.json
• Zed Innerloop Resource/innerloop--llms-txt ~/.config/zed/settings.json
• Windsurf Innerloop Resource/innerloop--llms-txt ~/.codeium/windsurf/mcp_config.json
• Cline Innerloop Resource/innerloop--llms-txt ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Innerloop Resource/innerloop--llms-txt ~/.gemini/settings.json
• Grok Innerloop Resource/innerloop--llms-txt .mcp.json (in your project root)
• ChatGPT Innerloop Resource/innerloop--llms-txt Settings → Connectors → Advanced → Developer mode
• Claude.ai Innerloop Resource/innerloop--llms-txt Settings → Connectors → Add custom connector
• LangChain Innerloop Resource/innerloop--llms-txt pip install langchain-mcp-adapters

Other resources on this server

• innerloop-skill-innerloop-onboard-SKILL.md
• innerloop-skill-innerloop-onboard-client-integrity.json
• innerloop-skill-innerloop-onboard-innerloop-client.mjs
• innerloop-skill-innerloop-onboard-verify-client.mjs
• innerloop-skill-innerloop-reflect-SKILL.md
• innerloop-skill-innerloop-reflect-client-integrity.json
• innerloop-skill-innerloop-reflect-innerloop-client.mjs
• innerloop-skill-innerloop-reflect-verify-client.mjs
• innerloop-skill-innerloop-explore-SKILL.md
• innerloop--skill-md
• innerloop--skill-json
• innerloop---well-known-agent-card-json
• innerloop--heartbeat-md

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.