FV Backlog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PREFIX | No | Optional string prefix to prepend to all tool names (default: ''). | |
| MAX_TOKENS | No | Set maximum token limit for responses (default: 50000). | |
| MCP_HTTP_HOST | No | HTTP bind address (default: 127.0.0.1). | |
| MCP_HTTP_PATH | No | URL path (default: /mcp). | /mcp |
| MCP_HTTP_PORT | No | HTTP port (default: 3333). | 3333 |
| MCP_TRANSPORT | No | MCP transport: 'stdio' (default) or 'http'. | |
| BACKLOG_DOMAIN | No | Your Backlog domain, e.g., your-domain.backlog.com. Required for single-organization and OAuth modes. | |
| BACKLOG_API_KEY | No | Your Backlog API key. Required for single-organization mode. Not required when OAuth is enabled. | |
| ENABLE_TOOLSETS | No | Comma-separated list of toolsets to enable (space, project, issue, wiki, git, notifications). Defaults to 'all'. | |
| DYNAMIC_TOOLSETS | No | Set to '1' to enable dynamic toolset discovery at runtime. | |
| OPTIMIZE_RESPONSE | No | Set to '1' to enable GraphQL-style field selection. | |
| BACKLOG_DEFAULT_ORG | No | Default organization name for multi-organization mode. | |
| MCP_SERVER_BASE_URL | No | Public URL of your MCP server (e.g., https://mcp.example.com). Required for OAuth. | |
| MCP_HTTP_ALLOWED_HOSTS | No | Comma-separated allowed Host hostnames. | |
| MCP_HTTP_JSON_RESPONSE | No | Set to 'true' to prefer JSON responses over SSE (2026-07-28 clients). | |
| BACKLOG_OAUTH_CLIENT_ID | No | OAuth Client ID from your Backlog application. | |
| BACKLOG_ALLOWED_PROJECTS | Yes | Comma-separated project keys this server may touch (e.g. PBL,INFRA). Required. Case-insensitive. Confines every tool to those projects. | |
| MCP_HTTP_ALLOWED_ORIGINS | No | Comma-separated allowed Origin hostnames for browser-based clients. | |
| BACKLOG_OAUTH_CLIENT_SECRET | No | OAuth Client Secret from your Backlog application. |
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/fv-forgevision/fv-backlog-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server