SameDayDesk agent tools

Official registry Productivity

Readiness checks, a paid Fix Pack, TaskMarket reads, and caller-declared funnel evidence.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http samedaydesk-agent-tools 'https://samedaydesk.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "samedaydesk-agent-tools": {
            "type": "http",
            "url": "https://samedaydesk.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. SameDayDesk (public entry)
  2. Docs (in-repo)
  3. Free / live vs offline fixtures
  4. Exact commands (clean checkout)
  5. Task → existing offer (cold selection)
  6. Verify the cited examples

SameDayDesk (public entry)

Public helpers for free discovery and offline result reuse. Node 22.x. The commands below use plain ESM under tools/; no npm install is required.

Start with the examples below, then open the helper documentation for options and error handling.

Docs (in-repo)

DocPurpose
tools/presence/FOR-AGENTS-COLD-READ.mdFree discovery when apex TLS/connect fails
tools/presence/REGISTRY-CONSUMER.mdMCP Registry version=latest pitfall
tools/result-reuse/README.mdOffline source → task-memory observation
tools/offer-routing/README.mdTask → existing SameDayDesk/Neomorphic offer
tools/offer-routing/capability-limits-matrix.jsonMachine-readable capability/limits matrix

Live free catalogs (no pay): https://agents.samedaydesk.com/llms.txt and https://agents.samedaydesk.com/.well-known/skills/index.json. Apex https://samedaydesk.com/for-agents may TLS/connect-fail; cold-read falls back to those alternates.

Free / live vs offline fixtures

ModeNetworkPaymentHow
Offline fixture cold-readnonenonepreferFixture: true → outcome: "offline_fixture"
Live cold-readfree HTTP onlynonedefault resolve → often alternate_live when apex fails
Result-reuse preview/exportnone (local JSON)nonefixtures + --opt-in to write

These helpers do not require a purchase. Paid extract/batch routes are separate.

Exact commands (clean checkout)

From the repository root (no install):

1. Offline cold-read (no network)
node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead({preferFixture:true}), null, 2))'

Expected: outcome: "offline_fixture", paid: false, liveObserved: false.

2. Live cold-read (free HTTP only; optional)
node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead(), null, 2))'

Expected when apex transport fails but agents.* respond: outcome: "alternate_live", paid: false.

3. Result-reuse preview and export on in-repo fixtures
PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
node tools/result-reuse/cli.mjs preview \
  --input tools/result-reuse/fixtures/accepted-page-change.json \
  --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW"

node tools/result-reuse/cli.mjs export \
  --input tools/result-reuse/fixtures/accepted-page-change.json \
  --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW" \
  --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-observation.json"
printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"

Record-kind fixture:

PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
node tools/result-reuse/cli.mjs export \
  --input tools/result-reuse/fixtures/accepted-record-report.json \
  --task-id vendor-watch --subject record-export --sequence 1 --clock "$NOW" \
  --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-record-observation.json"
printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"

Expected written observation: schema: "neomorphic.task-memory.observation.v1"; export requires --opt-in plus caller clock/task/subject/sequence.

Task → existing offer (cold selection)

When the job is known, route with the matrix before paying or treating a sample as live:

node tools/offer-routing/route-job.mjs tools/offer-routing/fixtures/complete-issue-discussion.job.json

Expected: ok: false, selected: null, exit code 2 and complete_issue_acquisition_unavailable. Neither paid /extract nor task-kit packaging acquires a complete discussion. This matrix does not advertise the pending issue-evidence acquisition pack. For historical fixture composition use fixtures/supplied-issue-brief.job.json under tools/offer-routing/. The MoltJobs SDK pack runs a disposable local HTTP rehearsal; its shipped runner refuses --live, even with credentials. Hosted archives are downloads, not hosted job execution. Routing does not evaluate acceptance criteria or authorize payment.

Verify the cited examples

npm run test:public-entry

That script runs the offline cold-read and fixture export commands cited above (no network, no payment). Existing focused suites: npm run test:presence, npm run test:result-reuse, npm run test:offer-routing.

Frequently asked questions

What is SameDayDesk agent tools?

Readiness checks, a paid Fix Pack, TaskMarket reads, and caller-declared funnel evidence.

How do I install SameDayDesk agent tools?

It runs as a remote server. In Claude Code: claude mcp add --transport http samedaydesk-agent-tools 'https://samedaydesk.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does SameDayDesk agent tools need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is SameDayDesk agent tools open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains SameDayDesk agent tools?

It is published by epistemedeus. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.