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