Job card vs Telesherpa Ontology Platform
A side-by-side look at the Job card and Telesherpa Ontology Platform MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Telesherpa Ontology PlatformSupport & Service ManagementOntology platform for field service: AI agents observe, connect and act on business objects.37FairAuth: not declaredVerdict: choose Job card for support & service management work as a local process; choose Telesherpa Ontology Platform for support & service management. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Job card when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
job_card_create, job_card_log_labor, job_card_log_material.
TChoose Telesherpa Ontology Platform when
- You need dedicated capabilities in the Support & Service Management domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Telesherpa Ontology Platform | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 52/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Job card | View Telesherpa Ontology Platform |
Tools & capabilities
Job card tools 10
job_card_createOpen a job card: client, site, what the job is, currency, scheduled date. Returns `JC-YYYY-NNNNjob_card_log_laborLog hours on a job card: who did the work, the day, the hours, the hourly rate in cents, what was donejob_card_log_materialLog materials used on a job card: the item, the quantity, the unit cost in centsjob_card_update_statusMove the card exactly one step -- open, in_progress, done, invoiced, archived -- stamping date and note into its historyjob_card_listList cards newest first with hours and totals; filter by status and client; totals kept per currencyjob_card_getRead one card in full: every entry, hours per worker, and the running totals in integer centsjob_card_printRender the card ready to print, with a signature line for client sign-off. Markdown or self-contained HTMLjob_card_deleteDelete a card entered by mistake. One holding labor or materials is refused; archive it insteadjob_card_summaryA day or a week: cards touched, hours per worker, labor and materials value per currency. A week runs Monday to Sundaylicense_statusFree or Pro, and the key
Telesherpa Ontology Platform 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.
Job card
{
"mcpServers": {
"job-card": {
"command": "npx",
"args": [
"-y",
"@theluckystrike/mcp-job-card"
]
}
}
}
Telesherpa Ontology Platform
No confirmed install command for Telesherpa Ontology Platform yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Job card is categorized under Support & Service Management and uses a local stdio subprocess. Telesherpa Ontology Platform belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Job card for support & service management work and Telesherpa Ontology Platform 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. Telesherpa Ontology Platform has no confirmed install command yet — follow its own setup instructions.
Job card has no declared pricing — check the project's own site. Telesherpa Ontology Platform is listed as a paid service. 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 job-card and telesherpa-ontology-platform as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Job card has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Telesherpa Ontology Platform has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.