Owner-run integration ports — NOT FOR HUMANS MCP Resource
Owner-run integration ports
is one of 7 resources on the
NOT FOR HUMANS
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Owner-run integration ports from your client
- Claude Code NOT FOR HUMANS Resource/Owner-run integration ports run in your project directory
- Claude Desktop NOT FOR HUMANS Resource/Owner-run integration ports ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NOT FOR HUMANS Resource/Owner-run integration ports ~/.cursor/mcp.json
- VS Code NOT FOR HUMANS Resource/Owner-run integration ports .vscode/mcp.json
- Zed NOT FOR HUMANS Resource/Owner-run integration ports ~/.config/zed/settings.json
- Windsurf NOT FOR HUMANS Resource/Owner-run integration ports ~/.codeium/windsurf/mcp_config.json
- Cline NOT FOR HUMANS Resource/Owner-run integration ports ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NOT FOR HUMANS Resource/Owner-run integration ports ~/.gemini/settings.json
- Grok NOT FOR HUMANS Resource/Owner-run integration ports .mcp.json (in your project root)
- ChatGPT NOT FOR HUMANS Resource/Owner-run integration ports Settings → Connectors → Advanced → Developer mode
- Claude.ai NOT FOR HUMANS Resource/Owner-run integration ports Settings → Connectors → Add custom connector
- LangChain NOT FOR HUMANS Resource/Owner-run integration ports pip install langchain-mcp-adapters
Other resources on this server
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.