MCP Client Setup
Detailed setup guide for connecting different MCP-compatible clients to PlusE HTTP Streamable Server.
MCP Client Setup Guide
This guide provides detailed instructions for connecting various MCP-compatible clients to PlusE's HTTP Streamable Server.
HTTP Streamable Server
PlusE provides an HTTP Streamable Server at:
https://mcp.plusefin.com/mcp/?apikey=YourAPIKey
Replace YourAPIKey
with your actual API key.
Supported Clients
Gemini CLI
Gemini CLI supports HTTP Streamable MCP servers using the httpUrl
configuration.
Setup Steps:
-
Install Gemini CLI
npm install -g @google/gemini-cli
-
Configure MCP Server Edit your
.gemini/settings.json
file to include:{ "mcpServers": { "plusefin": { "httpUrl": "https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY" } } }
Replace
YOUR_API_KEY
with your actual PlusE API key. -
Verify Connection
- Run
gemini-cli
and check that tools are available - Test by running a query that uses financial tools
- Run
Troubleshooting:
- Ensure the
httpUrl
is used instead ofurl
for HTTP Streamable servers - Verify your API key is correct
- Check network connectivity to
mcp.plusefin.com
Qwen (Local Model with MCP)
Qwen models (from Alibaba Cloud's QwenLM) can be integrated with MCP using local servers like llama.cpp for tool usage.
Setup Steps:
-
Install llama.cpp
git clone https://github.com/ggerganov/llama.cpp cd llama.cpp make
-
Download Qwen Model Download a GGUF version of Qwen model from Hugging Face (e.g., Qwen3-30B-A3B-GGUF).
-
Start Server with MCP
./llama-server --jinja -fa -hf unsloth/Qwen3-30B-A3B-GGUF:Q4_K_M -c 16384 --mcp-config config.json
Where
config.json
includes your HTTP Streamable MCP server:{ "mcpServers": { "plusefin": { "httpUrl": "https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY" } } }
-
Verify Connection
- Ensure the server starts successfully
- Test MCP tool calls in your application
Troubleshooting:
- Ensure model compatibility with MCP
- Check MCP configuration file syntax
- Verify API key and network access
- Refer to Qwen Code Docs for model specifics
Claude Desktop
Claude Desktop (from Anthropic) supports remote MCP servers directly via Connectors.
Setup Steps:
-
Open Claude Desktop
- Ensure you have Claude Desktop installed and logged in.
-
Add Connector
- Go to Settings > Connectors
- Click "Add Connector"
- Select "Remote MCP Server"
- Choose "HTTP Streamable" transport
- Enter the URL:
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- Replace
YOUR_API_KEY
with your actual PlusE API key.
-
Verify Connection
- The tools should appear in Claude Desktop's interface
- Test by asking Claude to use financial tools
Troubleshooting:
- Ensure your Claude plan supports remote MCP (Pro, Max, Team, Enterprise)
- Check the URL format
- Verify API key validity
Cherry Studio
Cherry Studio is an AI client that supports Streamable HTTP MCP protocol.
Setup Steps:
-
Install Cherry Studio
- Download and install Cherry Studio from its official website.
-
Configure MCP Servers
- Open Cherry Studio
- Navigate to Settings -> MCP Servers
- Add a new server with:
- Name: PlusEfin MCP
- URL:
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- Replace
YOUR_API_KEY
with your actual PlusE API key.
-
Verify Connection
- Check that tools are loaded in Cherry Studio
- Test tool usage in conversations
Troubleshooting:
- Ensure Cherry Studio is updated to support MCP
- Verify the URL and API key
- Check network connectivity
Other HTTP Streamable MCP-Compatible Clients
Other clients that support HTTP Streamable MCP can connect directly using the same URL format.
For Clients That Don't Support HTTP Streamable MCP
For AI clients that don't directly support HTTP Streamable MCP, use the mcp-remote
CLI tool to create a bridge to local stdio-based MCP clients:
Installation
npm install -g mcp-remote
Usage
To connect a local MCP client to the remote server:
npx mcp-remote https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY --transport http-only
This starts a local MCP server that your client can connect to via stdio. Configure your MCP client (like Claude Desktop) to use this local bridge.
For OAuth or other auth, check the mcp-remote documentation for additional options like --static-oauth-client-info
.
This approach allows any MCP-compatible client to access PlusE's HTTP Streamable MCP service through the mcp-remote bridge.
Configuration Options
Gemini CLI Configuration
httpUrl
:https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- API key is part of the URL
- Tools available in CLI environment
Qwen Configuration
- MCP config file with
httpUrl
:https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- API key is part of the URL
- Tools available in local model environment
- Refer to QwenLM Documentation
Claude Desktop Configuration
- Connector Type: Remote MCP Server
- Transport: HTTP Streamable
- URL:
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- API key is part of the URL
- Available in Settings > Connectors
Cherry Studio Configuration
- Settings: MCP Servers
- URL:
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- API key is part of the URL
- Streamable HTTP protocol supported
Clients Using mcp-remote
- CLI tool:
mcp-remote
- URL:
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
- --transport http-only flag for HTTP Streamable
- Local MCP server bridge for stdio clients
Security Best Practices
For HTTP Streamable Server:
- Keep your API key secure - it's part of the URL in configurations
- Use HTTPS connections only (URLs always start with
https://
) - Monitor your usage to prevent unauthorized access and detect anomalies
- For applications, use environment variables to store API keys instead of hardcoding
- For CLI tools like gemini-cli, ensure
.gemini/settings.json
is not committed to version control
For mcp-remote:
- The URL includes the API key, so treat the command-line invocation with care
- Use environment variables for API keys in scripts:
npx mcp-remote https://mcp.plusefin.com/mcp/?apikey=$PLUS_EFIN_API_KEY
- Avoid logging or exposing the full command with the API key
General Security:
- Never commit API keys to version control (use .gitignore for config files)
- Rotate API keys regularly to minimize exposure
- Use the principle of least privilege for API access
- Enable two-factor authentication on your PlusE account if available
- Regularly review and revoke unused API keys
Troubleshooting Common Issues
Connection Issues
-
Check the URL format - ensure it includes your API key
https://mcp.plusefin.com/mcp/?apikey=YOUR_API_KEY
-
Check your API key
- Ensure there are no extra spaces
- Verify the key format matches your account
- Confirm your account is active
-
Network connectivity
- Verify network configuration
- Check if there are any firewalls blocking the connection
Tool Not Appearing
- Wait for tool discovery - some clients need time to load tools
- Check client version - ensure your client supports HTTP Streamable MCP
- Verify the URL format - ensure the API key is properly appended
Authentication Errors
- Verify your API key is correct
- Check account status - ensure your account is active
- Confirm rate limits - check if you've exceeded your allowance
Support
If you encounter issues that aren't resolved by this guide:
- Join our community on Reddit
- Contact us via Telegram
- Create an issue in our GitHub repository
For more information about available tools, see our MCP Tools page.