MCP-Hound
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | HTTP server port (HTTP mode only) | 3000 |
| GITEA_URL | No | Gitea server URL (for file context) | |
| HOUND_URL | No | Hound server URL | http://localhost:6080 |
| GITHUB_URL | No | GitHub URL (for Enterprise, otherwise defaults) | https://github.com |
| GITEA_TOKEN | No | Gitea API token (for private repos) | |
| GITHUB_TOKEN | No | GitHub personal access token (for private repos) | |
| GITEA_TIMEOUT | No | Gitea API timeout (ms) | 10000 |
| HOUND_TIMEOUT | No | Request timeout (ms) | 30000 |
| GITHUB_TIMEOUT | No | GitHub API timeout (ms) | 10000 |
| HOUND_CONFIG_DIR | No | Path to Hound config directory (for auto-indexing) | |
| CORS_ALLOWED_ORIGIN | No | Allowed CORS origin (leave empty for permissive dev mode) | |
| HOUND_WEBHOOK_SECRET | No | Secret for Gitea webhook signature verification |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hound_searchA | Search code across all indexed repositories using regex patterns. Returns matching files and lines with deep links. |
| hound_reposA | List all repositories indexed by Hound code search. Returns repository names and URLs. |
| hound_file_contextB | Get extended context around a specific line in a file. Useful for understanding code around a search match. |
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 3 tools
Each tool has a clearly distinct purpose: listing repositories, searching code, and getting file context. There is no overlap or ambiguity.
All tools follow a consistent 'hound_' prefix with a verb_noun pattern (hound_file_context, hound_repos, hound_search), making them predictable and easy to differentiate.
With 3 tools, the set is well-scoped for a code search server. Each tool covers a necessary function without redundancy or bloat.
The tool set covers the core workflow of code search: listing repositories, searching, and examining context. There are no obvious gaps for the intended purpose.