Inclusify Accessibility vs Ovecc
A side-by-side look at the Inclusify Accessibility and Ovecc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Inclusify Accessibility for developer tools work over a hosted endpoint; choose Ovecc for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Inclusify Accessibility when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Choose Ovecc when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Inclusify Accessibility tools
No tool names declared yet. Check the project README from the listing page.
Ovecc tools
No tool names declared yet. Check the project README from the listing page.
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.
Inclusify Accessibility
{
"mcpServers": {
"inclusify-accessibility": {
"url": "https://app.inclusifyapp.com/api/mcp/customer"
}
}
}
Ovecc
{
"mcpServers": {
"ovecc": {
"command": "npx",
"args": [
"-y",
"ovecc"
]
}
}
}
Frequently asked questions
Inclusify Accessibility is categorized under Developer Tools and uses a remote HTTP/SSE transport. Ovecc belongs to Developer Tools and uses a local stdio subprocess. Pick Inclusify Accessibility for developer tools work and Ovecc for developer tools.
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.
Inclusify Accessibility has no declared pricing — check the project's own site. Ovecc is listed as free. Auth: no auth required. 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 inclusify-accessibility and ovecc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Inclusify Accessibility has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Ovecc has 45/100 (Fair) with 3 views, 2 installs and 3 GitHub stars.