Codegworkspace MCP vs Pushary
A side-by-side look at the Codegworkspace MCP and Pushary MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codegworkspace MCP for security work over a hosted endpoint; choose Pushary for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codegworkspace MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
register_agent_session, read_workspace_roster, write_handoff_note.
Choose Pushary when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PUSHARY_API_KEY. - You want tools like
send_notification, ask_user, wait_for_answer.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PUSHARY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 6 |
| Full listing | View Codegworkspace MCP | View Pushary |
Tools & capabilities
Codegworkspace MCP tools 4
register_agent_sessionread_workspace_rosterwrite_handoff_noteexport_session_summary
Pushary tools 6
send_notificationSend a push notification with optional rich context (file changes, errors, next steps)ask_userAsk the user a question via push - yes/no, multiple choice, or free textwait_for_answerLong-poll for the user's response to a questioncancel_questionCancel a pending question that's no longer relevantlist_sessionsRead-only view of your live agent sessions and pending questionspropose_scopeRatify the boundary of a run: file globs, enforced on supported hosts, or a recorded promise when the run changes no files
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codegworkspace MCP
{
"mcpServers": {
"codegworkspace-mcp": {
"url": "https://codegworkspace.clauxel.com/mcp"
}
}
}
Pushary
{
"mcpServers": {
"pushary": {
"command": "npx",
"args": [
"-y",
"pushary@latest"
],
"env": {
"PUSHARY_API_KEY": "YOUR_PUSHARY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Codegworkspace MCP is categorized under Security and uses a remote HTTP/SSE transport. Pushary belongs to Security and uses a local stdio subprocess. Pick Codegworkspace MCP for security work and Pushary for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codegworkspace MCP has no declared pricing — check the project's own site. Pushary has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add codegworkspace-mcp and pushary as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codegworkspace MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Pushary has 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars.