Under the Hood

The Under the Hood page provides technical access to PushBackLog internals, useful for developers and power users.

Accessing Under the Hood

Click Settings in the sidebar footer, then select Under the Hood; or click the </> icon directly.

OpenAPI / Swagger UI

The embedded Swagger UI shows the complete PushBackLog REST API specification:

• Browse all available endpoints
• See request/response schemas
• Try out API calls directly from the browser

Authorising API Calls in Swagger

1. Click the Authorize button in the top-right of the Swagger UI.
2. Enter your Bearer token (your Clerk session JWT).
3. Click Authorize and close the dialog.

All subsequent “Try it out” requests will include your token.

Getting Your Bearer Token

In the browser DevTools (F12), open the Network tab and look for any API request to api/v1/.... Find the Authorization: Bearer <token> header and copy the token value. Tokens are short-lived (typically 1 hour).

MCP Server (GitHub Copilot Integration)

PushBackLog ships an MCP (Model Context Protocol) server that integrates with GitHub Copilot and other AI assistants. This lets you interact with your backlog in natural language from within your IDE.

Connecting via MCP

Add the following to your VS Code .vscode/mcp.json:

{
  "servers": {
    "pushbacklog": {
      "type": "http",
      "url": "https://your-api-host/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Use an API key (not a session token) for long-lived MCP access. Generate an API key from Settings → API Keys.

Available MCP Tools

The MCP server exposes tools for all common operations:

• list_projects, get_backlog_item, create_backlog_item, update_backlog_item
• list_diary_entries, add_diary_entry
• list_time_entries, add_time_entry
• record_decision, list_decisions
• list_themes, create_theme, assign_theme
• list_personas
• And more — see the MCP tool listing in your IDE

API Keys

To generate a persistent API key for MCP or CI/CD use:

1. Go to Settings → API Keys.
2. Click New API Key.
3. Give it a descriptive name (e.g. “GitHub Copilot — dev machine”).
4. Copy the key immediately — it will not be shown again.
5. Store it securely (a password manager, not a config file committed to git).

API keys can be revoked at any time from the API Keys list.