Full-MCP-QA
by tamzidnahian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Email address associated with your Jira account | |
| JIRA_LABEL | No | Label used to filter Jira issues for autonomous testing (optional) | |
| TARGET_URL | Yes | The target website URL to test (default: https://news.ycombinator.com) | |
| GITHUB_REPO | No | GitHub repository for creating issues and PRs (optional) | |
| GITHUB_TOKEN | No | GitHub token for authentication (optional, alternative to GITHUB_PERSONAL_ACCESS_TOKEN) | |
| JIRA_BASE_URL | Yes | Your Jira instance base URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Jira API token for authentication | |
| OPENAI_API_KEY | Yes | Your OpenAI API key for generating tests | |
| SLACK_BOT_TOKEN | No | Slack bot token for notifications (optional, requires SLACK_CHANNEL_ID) | |
| JIRA_PROJECT_KEY | Yes | Jira project key for the project being tested | |
| SLACK_CHANNEL_ID | No | Slack channel ID for notifications (optional, requires SLACK_BOT_TOKEN) | |
| SLACK_WEBHOOK_URL | No | Slack webhook URL for notifications (optional, alternative to SLACK_BOT_TOKEN + SLACK_CHANNEL_ID) | |
| JIRA_WEBHOOK_SECRET | No | Secret for Jira webhook authentication (optional) | |
| JIRA_TRANSITION_DONE_ID | No | Transition ID to mark Jira issues as done upon passing tests (optional) | |
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub personal access token for authentication (optional, alternative to GITHUB_TOKEN) | |
| JIRA_AUTONOMOUS_FAILURE_LABEL | No | Label applied to issues that fail autonomous testing to prevent retries (optional) |
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
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
- 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/tamzidnahian/Full-MCP-QA'
If you have feedback or need assistance with the MCP directory API, please join our Discord server