docketeer-mcp
MCP (Model Context Protocol) server support for Docketeer. Connects the agent to any MCP-compatible server so new capabilities are config, not code.
Tools
| Tool | Purpose |
|---|---|
list_mcp_servers |
Show configured and connected servers |
connect_mcp_server |
Connect to a configured server |
mcp_oauth_complete |
Complete an OAuth flow for a server |
disconnect_mcp_server |
Disconnect from a server |
search_mcp_tools |
Semantic search across MCP server tools |
use_mcp_tool |
Call a tool on a connected server |
add_mcp_server |
Save a new server configuration |
remove_mcp_server |
Delete a server configuration |
Configuration
Server configs live in $DOCKETEER_DATA_DIR/mcp/ as individual JSON files.
Stdio server
{
"command": "uvx",
"args": ["mcp-server-time"],
"env": {"TZ": "America/New_York"},
"networkAccess": false
}
HTTP server
{
"url": "https://weather-api.example.com/mcp",
"headers": {"Authorization": "Bearer ..."}
}
Secrets stay in the data directory, outside the agent-visible workspace.
1 maintainer
Metadata
1 maintainer
Release files for docketeer-mcp 0.0.17
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| docketeer_mcp-0.0.17.tar.gz | 26.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docketeer_mcp-0.0.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.7 kB
Release files / docketeer_mcp-0.0.17.tar.gz
| Download URL | docketeer_mcp-0.0.17.tar.gz |
|---|---|
| Size | 26.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e13064a92417c8b38135781ffd223baa555c1af9e3ebc994902f20965b68974
|
|
BLAKE2b-256 checksum How to use checksums |
916d0c0ecb8446730b1a192404d0cc228d92216df75c03fa2be659abb2dcbbeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logRelease files / docketeer_mcp-0.0.17-py3-none-any.whl
| Download URL | docketeer_mcp-0.0.17-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01e7ef20897f30c38678e191234de4a3f77158730f29d239e915eb261c1e152a
|
|
BLAKE2b-256 checksum How to use checksums |
8efe88f4d11a31d5c92b2a60bab43d9ae8c53b6713a97b7342b4a942ebda8030
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logSecurity for docketeer-mcp 0.0.17
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for docketeer_mcp-0.0.17.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
