Learn how to use your deployed MCP tools
After deploying and connecting your MCP tools, you have multiple ways to access and use them. This guide covers the different methods of interacting with your tools.
All connected MCP tools are automatically available through the VeyraX API ecosystem. The VeyraX API provides a consistent interface for accessing all your tools through standard endpoints:
This method requires no additional setup beyond the initial connection and works automatically with all tools in your VeyraX account.
For targeted integration of specific MCP tools in your preferred environment, use the CLI installation command.
Implementation steps:
This adds just the specific tool to your chosen MCP client (Cursor, Claude, VS Code, etc.) without requiring the entire VeyraX ecosystem.
When you deploy an MCP tool with VeyraX, a unique SSE (Server-Sent Events) link is created for your tool. This link can be used with any MCP-compatible client:
This method enables direct integration without dependency on the VeyraX API infrastructure.
Each deployed MCP tool also exposes its own API endpoints that you can access directly:
This approach provides maximum flexibility for custom integrations and independent usage patterns.
Each access method serves different technical needs:
You can use different methods for different scenarios based on your technical requirements.
Learn how to use your deployed MCP tools
After deploying and connecting your MCP tools, you have multiple ways to access and use them. This guide covers the different methods of interacting with your tools.
All connected MCP tools are automatically available through the VeyraX API ecosystem. The VeyraX API provides a consistent interface for accessing all your tools through standard endpoints:
This method requires no additional setup beyond the initial connection and works automatically with all tools in your VeyraX account.
For targeted integration of specific MCP tools in your preferred environment, use the CLI installation command.
Implementation steps:
This adds just the specific tool to your chosen MCP client (Cursor, Claude, VS Code, etc.) without requiring the entire VeyraX ecosystem.
When you deploy an MCP tool with VeyraX, a unique SSE (Server-Sent Events) link is created for your tool. This link can be used with any MCP-compatible client:
This method enables direct integration without dependency on the VeyraX API infrastructure.
Each deployed MCP tool also exposes its own API endpoints that you can access directly:
This approach provides maximum flexibility for custom integrations and independent usage patterns.
Each access method serves different technical needs:
You can use different methods for different scenarios based on your technical requirements.