DevsContext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira email address | |
| JIRA_API_TOKEN | Yes | Your Jira API token | |
| SLACK_BOT_TOKEN | No | Your Slack bot token (optional) | |
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key for synthesis |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_task_contextA | Use this when starting work on a Jira ticket. Fetches and synthesizes everything you need: ticket requirements, acceptance criteria, discussion comments, related meeting transcripts, architecture docs, ADRs, and applicable coding standards. Call this FIRST when the user says 'work on PROJ-123' or 'start TICKET-456'. |
| search_contextA | Use this for freeform questions about the codebase, architecture, or past decisions. Searches across Jira tickets, meeting transcripts, and documentation. Use when the user asks questions like 'how do we handle errors?', 'what was decided about webhooks?', or 'why did we choose SQS?'. Input is a natural language question. |
| get_standardsA | Use this when checking coding conventions before or during implementation. Returns coding standards, style guides, and best practices from local docs. Filter by area: 'testing', 'error-handling', 'typescript', 'api', etc. Use when the user asks 'what are our testing conventions?' or 'how should I handle errors?' or before writing significant code. |
| devscontext_statusA | Check DevsContext configuration, source connectivity, and health status. Use this to verify your setup or debug connection issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: health check, coding standards, ticket context, and general search. Descriptions are precise and non-overlapping.
Most tools follow a verb_noun pattern (get_standards, get_task_context, search_context), but devscontext_status deviates with a server prefix and no verb, causing minor inconsistency.
Four tools cover the essential functionalities of a development context assistant without excess or deficiency, well-scoped for the domain.
The tool surface covers status checking, coding standards, Jira ticket context, and freeform search across multiple sources, leaving no obvious gaps for its intended use.