MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Open Sunsama is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for Open Sunsama - AI agent task and calendar management
Quickstart
# 1 — run it from where its publisher ships it
npx -y @open-sunsama/mcp
# 2 — ask your agent something
> MCP server for Open Sunsama - AI agent task and calendar management
Open Sunsama is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
OPAll 1 server
@open-sunsama1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Open Sunsama as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add open-sunsama-mcp -- npx -y @open-sunsama/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all subtasks for a specific task. Subtasks are checklist items within a task that help break down work into smaller actionable steps. Returns all subtasks with their completion status, title, and position.
Takes no parameters.
Example callreturns →
Create a new subtask within a task. Subtasks are smaller actionable items that help break down a task into manageable steps. Each subtask has a title and can optionally be positioned at a specific order within the task
Takes no parameters.
Example callreturns →
Toggle a subtask
Takes no parameters.
Example callreturns →
Update a subtask
Takes no parameters.
Example callreturns →
Permanently delete a subtask from a task. This action cannot be undone. Use this when a subtask is no longer needed or was created by mistake.
Takes no parameters.
Example callreturns →
List tasks with optional filters. Returns tasks sorted by position by default. Examples: - List today
Takes no parameters.
Example callreturns →
Get detailed information about a specific task by its ID. Returns the full task object including title, notes, scheduled date, priority, completion status, and timestamps. Example: {
Takes no parameters.
Example callreturns →
Create a new task. Required: title Optional: notes, scheduledDate, estimatedMins, priority Priority levels: - P0: Critical/Urgent (highest priority) - P1: High priority - P2: Medium priority (default) - P3: Low priority Examples: - Simple task: {
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Mark a task as complete. Sets the task
Takes no parameters.
Example callreturns →
Mark a task as incomplete (reopen a completed task). Clears the task
Takes no parameters.
Example callreturns →
Permanently delete a task. WARNING: This action cannot be undone. The task and all its subtasks will be permanently removed. Example: {
Takes no parameters.
Example callreturns →
Move a task to a specific date or to the backlog. This is a convenience tool for rescheduling tasks. Use it to: - Schedule a backlog task to a specific date - Reschedule a task to a different date - Move a scheduled task back to the backlog Examples: - Schedule for tomorrow: {
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List time blocks from your calendar with optional filters. Use this tool to: - View all time blocks for a specific date (use
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Update an existing time block
Takes no parameters.
Example callreturns →
Delete a time block from your calendar. Use this tool to: - Remove a scheduled time block that
Takes no parameters.
Example callreturns →
Link a task to a time block, or unlink a task from a time block. Use this tool to: - Connect a scheduled time block to a specific task you
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get the current authenticated user
Takes no parameters.
Example callreturns →
Update the current user
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Open Sunsama costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 98 / 100
Release 1.0.0 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score98
Findings2 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationnone
Surface digesta348bc166bc68cbff41956346c9cc2a29d2d150450ac7db9c8a75b993cbb9497
Score vectorthreat 100 → client 98
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_subtasks | no tags | |
| create_subtask | no tags | |
| toggle_subtask | no tags | |
| update_subtask | no tags | |
| delete_subtask | no tags | |
| list_tasks | no tags | |
| get_task | no tags | |
| create_task | no tags | |
| update_task | no tags | |
| complete_task | no tags | |
| uncomplete_task | no tags | |
| delete_task | no tags | |
| schedule_task | no tags | |
| reorder_tasks | no tags | |
| list_time_blocks | no tags | |
| get_time_block | no tags | |
| create_time_block | no tags | |
| update_time_block | no tags | |
| delete_time_block | no tags | |
| link_task_to_time_block | no tags | |
| get_schedule_for_day | no tags | |
| get_user_profile | no tags | |
| update_user_profile | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta348bc166bc68cbf
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Open Sunsama in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.