Directory / Work & productivity
AI Tasker
Hosted MCP server for coordinating AI-agent work with projects, tasks, dependencies, workspaces, identities, budgets, evidence, and lifecycle operations; API key required. Endpoint: https://mcp.ai-tasker.theboomer.dev/mcp
Needs auth Reachable, and asks for credentials before it will talk. Tools were not inspected.
- Category
- Work & productivity
- Transport
http- Source
- https://ai-tasker.theboomer.dev
- Endpoint
https://mcp.ai-tasker.theboomer.dev/mcp- MCP Registry
dev.theboomer/ai-tasker- Handshake time
- 384 ms
- Last checked
- 2026-11-03 10:54:33 UTC
- Listed since
- 2026-10-21
Health and compatibility
| Endpoint reachable | Verified | Responded in 384 ms |
|---|---|---|
| MCP handshake (initialize) | Untested | The server asks for an API key or token first |
| Tool discovery (tools/list) | Untested | Not attempted |
| Authentication | Verified | Requires an API key or token |
| Protocol version | Untested | Only known after a completed handshake |
| Transport | Untested | Listed as http |
Last checked . Verified means the check saw it happen; it says nothing about whether the server is safe.
Recent history
100% of the last 9 daily checks reachable; median response 469 ms. Green answered, violet asked for auth, red did not answer.
Set up in your client
Claude Code
Run this in a terminal:
claude mcp add --transport http ai-tasker https://mcp.ai-tasker.theboomer.dev/mcp --header "Authorization: Bearer YOUR_TOKEN"Claude Desktop
Open Settings → Connectors → Add custom connector and paste this URL:
https://mcp.ai-tasker.theboomer.dev/mcpOr bridge it through mcp-remote in claude_desktop_config.json (needs Node.js):
{
"mcpServers": {
"ai-tasker": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.ai-tasker.theboomer.dev/mcp",
"--header",
"Authorization: Bearer YOUR_TOKEN"
]
}
}
}Cursor
Or add it to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"ai-tasker": {
"url": "https://mcp.ai-tasker.theboomer.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}VS Code
Or add it to .vscode/mcp.json:
{
"servers": {
"ai-tasker": {
"type": "http",
"url": "https://mcp.ai-tasker.theboomer.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Or from a terminal:
code --add-mcp '{"name": "ai-tasker", "type": "http", "url": "https://mcp.ai-tasker.theboomer.dev/mcp", "headers": {"Authorization": "Bearer YOUR_TOKEN"}}'Windsurf
Add it to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"ai-tasker": {
"serverUrl": "https://mcp.ai-tasker.theboomer.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Other clients
Most clients accept this shape. The endpoint is:
https://mcp.ai-tasker.theboomer.dev/mcp{
"mcpServers": {
"ai-tasker": {
"type": "http",
"url": "https://mcp.ai-tasker.theboomer.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}If it does not connect
- This server asked for credentials. Replace
YOUR_TOKENwith your own key. A bearer token is the usual form, but check the server's documentation for the exact header it expects. - Restart the client after editing a config file, and keep keys out of files you commit.
- If the tools do not appear, open the client's MCP log: a 401 means the credentials were not accepted, and a timeout means the server did not answer.
Badge
Maintain this server? Put its live status in your README:
[](https://mcp.aianytime.net/s/ai-tasker/)Edit this entry · Report a problem
More in Work & productivity
Checks record what a server answered, not whether it is safe. A listing is not a security audit; read a server's source and permissions before you connect it. Add a server · JSON · llms.txt · llms-full.txt
Browse: Agents, IDEs & developer tools · Search & discovery · Knowledge, memory & context · Media & generation · Security · Finance & markets · Marketing, content & social · Cloud, ops & data · Commerce, travel & logistics · Work & productivity · No account needed · Local servers