Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y [email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add mite-mcp -- npx -y mite-mcp@1.0.2टर्मिनल में चलाएँ।
{ "mcpServers": { "mite-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
MCP server in TypeScript to allow agents to interact with mite.de.
Published to npm, so no clone or build is needed — point your MCP client at it with npx and supply
your own credentials. MITE_ACCOUNT is your {account}.mite.de subdomain; MITE_API_KEY is your
mite API key (mite → your user menu → API key; an admin may need to enable API access).
MCP to allow agents interact with mite.de
{
"mcpServers": {
"mite": {
"command": "npx",
"args": ["-y", "mite-mcp"],
"env": {
"MITE_ACCOUNT": "your-account",
"MITE_API_KEY": "your-api-key"
}
}
}
}
In Claude Code, the equivalent one-liner:
claude mcp add mite \
--env MITE_ACCOUNT=your-account \
--env MITE_API_KEY=your-api-key \
-- npx -y mite-mcp
Verify with /mcp (Claude Code) and try the whoami tool first — it confirms your credentials and
account. For pinning a per-repo default project/service, see Per-repo defaults
below (set MITE_DEFAULT_SCOPE and run against the local dist/index.js).
npm install
npm run dev
npm run build
npm run lint
npm run format
npm test
npm start
Naming the project and service on every create_time_entry is friction. Bind a working context
(usually a repository) to a default project + service once, and the dominant create flow needs no
ids. See ADR-0005.
The scope is the key that binds a context to its default. It is resolved from the environment — never authored by the agent — by this priority chain, so it never drifts:
scope argument (advanced / future global mode — normally omitted);MITE_DEFAULT_SCOPE environment variable (set in the repo's .mcp.json);set_default.Defaults are stored in ~/.config/mite-mcp/defaults.json (honoring XDG_CONFIG_HOME), shaped
{ "scopes": { "<key>": { "project_id", "service_id" } } }. Only project + service are stored — the
customer is derivable. Writes are atomic (write-temp-then-rename), so multiple server processes may
share the file safely.
Run the server inside the repo and call the tools (the agent omits scope):
set_default({ project_id, service_id }) — binds the resolved scope and returns the resolved
project and service names so you can confirm what was stored.get_default() — shows the current scope's default (or a structured response naming existing
scopes if none is set).clear_default() — removes it.list_defaults() — lists every stored scope.Then create_time_entry({ minutes: 90, note: "work" }) logs against the default and echoes the
resolved project/service names. If no default exists, you get an actionable prompt to set one rather
than an error.
.mcp.jsonRun the server per repo with a project-scoped .mcp.json. Setting MITE_DEFAULT_SCOPE pins the
scope key explicitly (step 2), which is the most reliable option:
{
"mcpServers": {
"mite": {
"command": "node",
"args": ["/absolute/path/to/mite-mcp/dist/index.js"],
"env": {
"MITE_ACCOUNT": "your-account",
"MITE_API_KEY": "your-api-key",
"MITE_DEFAULT_SCOPE": "acme-web"
}
}
}
}
Build first with npm run build, then point args at the built dist/index.js (the same entry
npm start runs). MITE_ACCOUNT is your {account}.mite.de subdomain and MITE_API_KEY your mite
API key. You can omit MITE_DEFAULT_SCOPE and let the scope fall through to the git remote / repo
path instead.
Releases are automated with semantic-release on every push
to main (.github/workflows/release.yml). The version bump is derived from
Conventional Commit messages since the last release:
fix: → patch, feat: → minor, feat!: / BREAKING CHANGE: → major;docs: / chore: / refactor: / test: → no release.When a release is warranted the pipeline bumps package.json, updates CHANGELOG.md, tags the
commit, publishes to npm, and creates a GitHub release — no manual step. The only prerequisite is an
npm automation token stored as the NPM_TOKEN repository secret (GITHUB_TOKEN is provided
automatically). Do not bump the version by hand; the pipeline owns it.
{ "mcpServers": { "mite-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Mite stdio पर लोकल चलता है।
पिछली जाँच 2026-11-14 को हुई। MCP to allow agents interact with mite.de