getting-started — EveryInfra MCP Resource
getting-started
is one of 6 resources on the
EveryInfra
MCP server. Connect the server and your client can attach it as context.
by client
How to attach getting-started from your client
- Claude Code EveryInfra Resource/getting-started run in your project directory
- Claude Desktop EveryInfra Resource/getting-started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EveryInfra Resource/getting-started ~/.cursor/mcp.json
- VS Code EveryInfra Resource/getting-started .vscode/mcp.json
- Zed EveryInfra Resource/getting-started ~/.config/zed/settings.json
- Windsurf EveryInfra Resource/getting-started ~/.codeium/windsurf/mcp_config.json
- Cline EveryInfra Resource/getting-started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EveryInfra Resource/getting-started ~/.gemini/settings.json
- Grok EveryInfra Resource/getting-started .mcp.json (in your project root)
- ChatGPT EveryInfra Resource/getting-started Settings → Connectors → Advanced → Developer mode
- Claude.ai EveryInfra Resource/getting-started Settings → Connectors → Add custom connector
- LangChain EveryInfra Resource/getting-started pip install langchain-mcp-adapters
Other resources on this server
EveryInfra also offers 7 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 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.