Filesystem vs MCP Tomticket
A side-by-side look at the Filesystem and MCP Tomticket MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose MCP Tomticket for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Choose MCP Tomticket when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tomticket_list_open_tickets, tomticket_list_tickets, tomticket_get_ticket.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | Support & Service Management |
| Quality signal | 85/100 · Excellent | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,526 | 0 |
| Directory activity | 11 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 49 |
| Full listing | View Filesystem | View MCP Tomticket |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
MCP Tomticket tools 49
tomticket_list_open_ticketsLista chamados ABERTOS da conta TomTicket (exclui cancelados e finalizados). Nao altera dados.tomticket_list_ticketsLista chamados da conta com filtros da API (paginado, 50 por pagina). Nao altera dados.tomticket_get_ticketConsulta o detalhe completo de um chamado, incluindo respostas e horarios. Nao altera dados.tomticket_create_ticketATENCAO: altera producao. Cria um novo chamado no TomTicket.tomticket_reply_ticketATENCAO: altera producao. Responde o chamado como atendente. Exige atendente vinculado. Use start_date e end_date juntos para lancar horario de trabalho.tomticket_reply_ticket_as_customerATENCAO: altera producao. Responde o chamado como cliente. Nao dispara email automaticamente.tomticket_comment_ticketATENCAO: altera producao. Adiciona comentario interno no chamado.tomticket_finish_ticketATENCAO: altera producao. Finaliza o chamado. time_work lanca minutos trabalhados. Nao dispara email automaticamente.tomticket_evaluate_ticketATENCAO: altera producao. Avalia um chamado ja finalizado.tomticket_transfer_ticketATENCAO: altera producao. Transfere o chamado entre departamentos e/ou atendentes.tomticket_assign_operatorATENCAO: altera producao. Vincula um atendente ao chamado.tomticket_start_statusATENCAO: altera producao. Abre um status no chamado (inicia cronometro/status). Consulte status do departamento antes.- +37 more on 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.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
MCP Tomticket
{
"mcpServers": {
"mcp-tomticket": {
"command": "npx",
"args": [
"-y",
"mcp-tomticket"
]
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. MCP Tomticket belongs to Support & Service Management and uses a local stdio subprocess. Pick Filesystem for file systems work and MCP Tomticket for support & service management.
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.
Filesystem is listed as free. Auth: no auth required. MCP Tomticket 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 filesystem and mcp-tomticket as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 85/100 (Excellent) with 11 views, 0 installs and 91,526 GitHub stars. MCP Tomticket has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.