@cqnce/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CQNCE_API_KEY | No | Project API key — grants access to request submission and monitoring | |
| CQNCE_BASE_URL | Yes | Base URL of your cQnce backend (e.g. https://api.example.com) | |
| CQNCE_ADMIN_TOKEN | No | Tenant admin JWT — grants access to project, agent, team, and callback management |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_authorization_requestA | Submit a human authorization request to cQnce. Use this BEFORE performing any risky, destructive, or irreversible action (e.g. deploying to production, executing a database migration, making a payment, modifying credentials). Returns a requestId that you can pass to wait_for_approval or poll_request_status. |
| poll_request_statusA | Check the current status of a cQnce authorization request. Terminal statuses are: APPROVED, REJECTED, EXPIRED, CANCELLED. PENDING means the request is still waiting for a human decision. For a blocking wait, use wait_for_approval instead. |
| wait_for_approvalA | Submit an authorization request and BLOCK until a human approves or rejects it (or until the timeout elapses). This is the primary tool for human-in-the-loop workflows: call it, wait for the result, and proceed ONLY if status is APPROVED. If status is REJECTED or EXPIRED, do NOT proceed with the action. |
| cancel_requestA | Cancel a pending cQnce authorization request. Use this if the action is no longer needed and you want to release the human agents. |
| list_requestsA | List authorization requests for this project. Useful for monitoring ongoing requests, debugging workflows, and auditing decisions. |
| get_requestA | Get full details of a single authorization request, including payload, metadata, agent responses, and current status. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/cqnce-app/cqnce-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server