Skip to main content
Use tk with Goose to manage issues from Block’s open-source AI coding agent.

​
What is Goose?

Goose is a free, open-source AI coding agent built by Block (formerly Square). It features an MCP-native architecture — every extension is an MCP server — making it one of the most natural integration points for tk. Goose runs as a desktop app or CLI and connects to 3,000+ MCP servers.

​
MCP Integration

​
Quick Setup (CLI)

Run the interactive configuration: 
goose configure
Select Add custom extension > Command-line Extension, then enter:
  • Name: ticket-mcp
  • Command: uvx ticket-mcp

​
Manual Configuration

Edit ~/.config/goose/config.yaml: 
extensions:
  ticket-mcp:
    name: ticket-mcp
    cmd: uvx
    args: [ticket-mcp]
    enabled: true
    type: stdio
    timeout: 300
uv installed via: curl -LsSf https://astral.sh/uv/install.sh | shPython version 3.10 or higher (installed automatically by uv)Goose installed from block.github.io/goose

​
Verify Installation

Run goose info -v to confirm ticket-mcp appears in the extensions list, then start a session: 
goose session
Ask: “What tk tools are available?” — Goose should list all ticket-mcp tools.

​
Workflow Tips

​
Starting a Session

Ask Goose: “Run tk triage and show me what I should work on today” Goose will execute tk triage and present AI-powered recommendations.

​
Creating Issues

Ask Goose: “Create a high-priority bug for the database connection leak” Goose will run: 
tk create "Fix database connection leak" -t bug -p 1

​
Closing Work

Ask Goose: “Resolve tk-abc123, the fix is deployed” Goose will run tk resolve tk-abc123 and report newly unblocked issues.

​
Dependency Management

Ask Goose: “Show the dependency tree for tk-xyz789 and explain what’s blocking it”

​
Project Health

Ask Goose: “Run tk insights and tell me about the project’s bottlenecks”

​
Goose-Specific Features

Goose treats every extension as an MCP server. This means ticket-mcp is a first-class citizen — not an adapter or wrapper, but a native integration that Goose can reason about and compose with other MCP tools.
Goose’s desktop app provides a visual interface for managing extensions. You can enable/disable ticket-mcp, view tool invocations, and manage sessions through a GUI.
Goose can compose multiple MCP servers in a single session. Combine ticket-mcp with GitHub, database, or cloud extensions for end-to-end workflows like “create an issue, fix it, push to GitHub, and resolve.”
Goose recommends limiting active extensions to 5 or fewer with 50 or fewer total tools for optimal performance. ticket-mcp is lightweight and fits well within these limits.

​
Troubleshooting

Run goose info -v to check extension status. Ensure uvx is in your PATH. Try increasing the timeout value in config.yaml if the server is slow to start on first run (it needs to download dependencies).
Goose uses YAML (not JSON) for configuration. Verify indentation is correct — YAML is whitespace-sensitive. Use goose configure for the interactive setup to avoid syntax issues.
Ensure enabled: true in your config.yaml. Start a new session with goose session after changing configuration.
Enable caching with tk cache info to verify the analytics cache is working. Cached responses return in under 10ms.

​
Next Steps

CLI Reference

Complete tk command documentation

MCP Server

Deep dive into MCP server capabilities

Graph Analytics

Learn about PageRank and dependency analysis

Goose Docs

Official Goose documentation

​
Sources