devflow-mcp
by channen2
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | The account email tied to the Jira API token. | |
| GITHUB_TOKEN | No | Fine-grained personal access token for GitHub with Pull requests (Read and write) and Checks (Read-only) permissions. | |
| JIRA_BASE_URL | No | Jira base URL, e.g. https://your-domain.atlassian.net | |
| JIRA_API_TOKEN | No | Jira API token from id.atlassian.com → Security → API tokens. | |
| SLACK_BOT_TOKEN | No | Slack Bot User OAuth token with at least chat:write scope. |
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
- 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/channen2/dev-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server