Productivity · Local MCP server
Mycase MCP
Connect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.oktopeak/mycase-mcp- Version
- 1.0.4
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-15
- Updated
- 2026-05-15
- Publisher
- oktopeak (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/oktopeak) · how
- Listed under
- Calendar MCP servers
- Repository
- github.com/oktopeak/mycase-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @oktopeak/mycase-mcp | 1.0.4 | stdio |
How to connect Mycase MCP
Mycase MCP runs locally from a Node.js package published to the npm registry: @oktopeak/mycase-mcp version 1.0.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @oktopeak/mycase-mcp@1.0.4. It reads these environment variables: MYCASE_CLIENT_ID (required), MYCASE_CLIENT_SECRET (required, secret), ENCRYPTION_KEY (required, secret), MYCASE_REDIRECT_PORT and MYCASE_EXPERIMENTAL_TOOLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mycase-mcp": {
"command": "npx",
"args": [
"-y",
"@oktopeak/mycase-mcp@1.0.4"
],
"env": {
"MYCASE_CLIENT_ID": "<value>",
"MYCASE_CLIENT_SECRET": "<secret>",
"ENCRYPTION_KEY": "<secret>",
"MYCASE_REDIRECT_PORT": "<value>",
"MYCASE_EXPERIMENTAL_TOOLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from oktopeak (GitHub)
| Server | Runs |
|---|---|
| Clio MCPConnect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. | Local · stdio |
| Filevine MCPOpen-source MCP server connecting Claude to Filevine practice management. Built by Oktopeak. | Local · stdio |
| IntakeQ MCPIntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write. | Local · stdio |
| Lawmatics MCPConnect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices. | Local · stdio |
More productivity servers
| Server | Runs |
|---|---|
| MutatorBuild and test short-form marketing automations from your agent. Nothing it does can post. | Remote · HTTPLive check: sign-in required |
| MX ProbeEmail verification for AI agents: send, hold or kill with the reason. Signup and credits by API. | Local · stdio |
| myagentinboxDisposable email inboxes for AI agents. Auto-deletes after 24 hours. | Remote · HTTPLive check: ✗ no handshake |
| MycTask queue, decisions and memory for coding agents. Local SQLite, no network. Requires Bun. | Local · stdio |
| MyClawn ComputerYour own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs. | Remote · HTTPLive check: sign-in required |
| MyPennyPortable AI memory you own. Keep memories and notes across Claude, ChatGPT, and other AI tools. | Remote · HTTPLive check: ✓ handshake |
| myplanShared Markdown notes and canvases that people and AI agents edit together; agents suggest edits. | Remote · HTTPLive check: sign-in required |
| Mytown MCPUS & Canadian local-government meetings, decisions & place context from official sources. | Local · stdio |