tuskr-mcp-server
Provides an MCP (Model Context Protocol) server that connects an MCP client to the Tuskr REST API, supporting bearer token authentication and configurable MCP transport (HTTP or stdio).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses bearer tokens via Authorization header and suggests environment-variable-based configuration (good for avoiding hardcoded secrets). However, README does not explicitly require HTTPS for the HTTP transport, does not describe token handling practices (e.g., logging/redaction), and does not mention rate limiting, scopes, or other security controls. Transport choices include stdio for local dev, which can reduce exposure over the network but may increase operational risk if misconfigured.
⚡ Reliability
Best When
You want to expose Tuskr functionality to MCP clients either locally (stdio) or over HTTP, and you can manage access tokens via environment variables.
Avoid When
You cannot ensure HTTPS-only deployment for the HTTP MCP transport or you need clearly documented rate limit semantics, error codes, and retry behavior.
Use Cases
- • Use Tuskr REST API capabilities from an MCP-enabled agent/tooling environment
- • Local development of MCP tools via stdio transport
- • Running a networked MCP server that proxies requests to Tuskr using access tokens
Not For
- • Production deployments where you need a fully documented/typed REST/SDK surface for the MCP server itself beyond the README examples
- • Use cases requiring fine-grained OAuth scopes or SSO (not described)
- • Environments that require explicit retry/idempotency guarantees from the MCP server (not documented)
Interface
Authentication
Authentication is described as an access token (Bearer) plus an optional Account-ID header backed by TUSKR_ACCOUNT_ID. No OAuth flows or scope granularity are described.
Pricing
No pricing information provided for this MCP wrapper itself; assumes Tuskr API pricing applies separately.
Agent Metadata
Known Gotchas
- ⚠ HTTP transport URL/path is shown as /mcp/—ensure clients match that exact path
- ⚠ The README mandates Authorization and optionally uses Account-ID via header/server-side env var; missing/incorrect headers may prevent calls
- ⚠ No documented rate limit or retry/idempotency semantics for the MCP server—agents may need conservative retry/backoff handling themselves
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for tuskr-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.