getting-started — CurrencyCore MCP Resource
getting-started
is one of 25 resources on the
CurrencyCore
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 CurrencyCore Resource/getting-started run in your project directory
- Claude Desktop CurrencyCore Resource/getting-started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CurrencyCore Resource/getting-started ~/.cursor/mcp.json
- VS Code CurrencyCore Resource/getting-started .vscode/mcp.json
- Zed CurrencyCore Resource/getting-started ~/.config/zed/settings.json
- Windsurf CurrencyCore Resource/getting-started ~/.codeium/windsurf/mcp_config.json
- Cline CurrencyCore Resource/getting-started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CurrencyCore Resource/getting-started ~/.gemini/settings.json
- Grok CurrencyCore Resource/getting-started .mcp.json (in your project root)
- ChatGPT CurrencyCore Resource/getting-started Settings → Connectors → Advanced → Developer mode
- Claude.ai CurrencyCore Resource/getting-started Settings → Connectors → Add custom connector
- LangChain CurrencyCore Resource/getting-started pip install langchain-mcp-adapters
Other resources on this server
- ai-credits
- ai-endpoint
- authentication
- billing
- byok
- code-examples
- convert-endpoint
- correlation-endpoint
- countries
- currencies
- drawdown-endpoint
- errors
- history-analysis-endpoint
- history-endpoint
- mcp
- mean-reversion-endpoint
- ppp-analysis-endpoint
- rates-endpoint
- safe-haven-endpoint
- sdks
- spreadsheets
- sso
- volatility-endpoint
- openapi
CurrencyCore also offers 4 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 10 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.