Nexian MCP Hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_URL | Yes | The backend API URL for the core services. | |
| APP_URL | Yes | The URL of the web application (e.g., Vercel web URL). | |
| MCP_URL | No | The URL of the MCP service. | |
| SESSION_SECRET | Yes | A shared secret for sessions that must match between the API and MCP services. | |
| NEXT_PUBLIC_API_URL | Yes | The public API URL used by the frontend to point to the backend API. | |
| NEXT_PUBLIC_MCP_URL | Yes | The public MCP URL used by the frontend to point to the MCP invoke service. | |
| HALOPSA_REDIRECT_URI | No | The redirect URI for HaloPSA integration, pointing to the API callback URL. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nexiantechnology697531971/mcphub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server