MCP Secure Local Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| policy | No | Path to a custom security policy configuration file in YAML format. If not provided, the server runs with its built-in default policy. |
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 |
|---|---|
| search_toolsA | Search for available tools by keyword or category. Use detail_level to control how much information is returned: 'name' for just tool names, 'summary' for names and descriptions, 'full' for complete definitions including input schemas. |
| list_categoriesA | List all available tool categories (plugins) with their tool counts. Use this to discover what capabilities are available before searching. |
| web_searchB | Search the web using DuckDuckGo. Returns titles, URLs, and snippets. |
| init_bugtrackerC | Initialize bug tracker for a project. Creates .bugtracker/ directory. |
| add_bugC | Add a new bug to the tracker. |
| get_bugC | Get a bug by ID. |
| update_bugB | Update an existing bug. Can update status, priority, tags, related_bugs. Supports note-only updates for progress tracking. |
| close_bugA | Close a bug (convenience wrapper for update_bug with status=closed). |
| list_bugsC | List bugs with optional filtering by status, priority, and tags. |
| search_bugs_globalC | Search bugs across all indexed projects. |
| configure_figma_storiesC | Configure Figma Stories plugin with API tokens and AI settings. Set FIGMA_API_TOKEN environment variable for Figma access. |
| generate_user_storiesC | Generate agile user stories from a Figma design file. Creates markdown file with stories, epics, and acceptance criteria. |
| preview_user_storiesA | Preview generated user stories without writing to file. Shows first 3 stories per epic. |
| list_figma_pagesC | List pages in a Figma file for selection. |
| get_config_statusB | Get current configuration 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 | |
TDQS
Scored across 15 tools
The tool set has clear distinct purposes for most tools, but some overlap exists, such as 'close_bug' being a convenience wrapper for 'update_bug', which could cause confusion in selection. However, descriptions help clarify these relationships, and tools like 'configure_figma_stories' and 'generate_user_stories' are well-differentiated within their domain.
Most tools follow a consistent verb_noun pattern, such as 'add_bug', 'get_bug', 'list_bugs', and 'update_bug', with minor deviations like 'configure_figma_stories' and 'preview_user_stories' that still maintain readability. The naming is largely predictable and coherent across the set.
With 15 tools, the count is well-scoped for a server handling bug tracking, Figma integration, and general utilities. Each tool appears to earn its place by covering specific operations without feeling excessive or thin for the apparent scope of the server.
The server provides good coverage for bug tracking with CRUD operations and additional features like searching and configuration. Minor gaps exist, such as no explicit tool for deleting bugs or managing Figma projects beyond the listed operations, but agents can likely work around these with the available tools.