Discoverable tools
The tools currently available to Jcode agents, with the same descriptions and setup instructions returned by discover_tools.
Jcode partner listings. Partnership status never influences recommendations. How partnerships and revenue sharing work.
-
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
CLI: npm install -g agent-cards-admin, then agent-cards-admin login (magic link; user clicks it). Integration guide for agents: https://docs.agentcard.sh/companies/integration-guide.md. Full docs: https://docs.agentcard.sh
-
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Complete agent setup protocol (no additional documentation fetch is required): 1. Run gh --version. If gh is missing, ask for confirmation before installing software, then use the operating system's package manager from https://github.com/cli/cli/blob/trunk/docs/install_linux.md or https://cli.github.com/ and verify gh --version succeeds. 2. Run gh auth status. If the user is already authenticated for the required GitHub host, continue without displaying or reading their token. 3. If authentication is missing, tell the user to run gh auth login in their own interactive terminal and complete the browser or device-code flow. Never request, print, persist, or commit a GitHub token. Re-run gh auth status after the user confirms completion. 4. Work from the target repository when possible. Use explicit --repo OWNER/REPO outside a repository. Before a write operation, inspect the current account and target repository with gh auth status and gh repo view --json nameWithOwner,url. 5. Use the narrowest command for the task: gh pr for pull requests, gh issue for issues, gh run or gh workflow for Actions, gh release for releases, gh repo for repositories, and gh api only when a dedicated command is unavailable. 6. Treat repository creation or deletion, merges, releases, workflow dispatches, permission changes, and other remote mutations as consequential. Show the exact target and obtain explicit user confirmation immediately before the action when confirmation is required. Official manual: https://cli.github.com/manual/. Authentication reference: https://cli.github.com/manual/gh_auth.
-
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Complete agent setup protocol (no additional documentation fetch is required): 1. Work from the Git repository the user wants reviewed. Check node --version and require Node 22 or newer. 2. Check greptile --version. If Greptile is missing or older than 3.2.0, ask for confirmation before installing software, then run npm install -g [email protected] and verify the installed version. 3. Run greptile whoami. If it reports that the user is not signed in, tell the user to run greptile login in their own interactive terminal, complete the browser approval, and confirm when greptile whoami shows their account. Do not attempt to bypass the interactive sign-in. 4. Run greptile onboard as a read-only state probe. In an agent or non-TTY environment it prints onboarding status instead of opening the wizard. 5. If onboarding is incomplete, explain that it creates a Greptile organization, connects GitHub or GitLab, grants repository access, imports supported AI rules files, and starts a 14-day free trial with no payment method required. After the user confirms, tell them to run cd [repo-root] && greptile onboard in their own interactive terminal. Wait for them to confirm that setup completed. 6. Re-run greptile onboard and proceed only when it reports complete. Run greptile review --agent from the repository root, then summarize the findings for the user's original task. Official onboarding playbook: https://www.greptile.com/docs/code-review/cli-onboarding. CLI reference: https://www.greptile.com/docs/code-review/greptile-cli.
-
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Agent setup protocol (Browser Use Cloud, API v3): 1. Auth uses an API key (prefix bu_) in the X-Browser-Use-API-Key header. If BROWSER_USE_API_KEY is already set, skip to step 4. 2. If the user has an account, ask them to create a key at https://cloud.browser-use.com/settings?tab=api-keys&new=1 and export BROWSER_USE_API_KEY. Never print or commit the key. 3. Alternatively, an agent can self-provision a free account: POST https://api.browser-use.com/cloud/signup (optional JSON {"email":"<user email>","name":"<user name>"}) returns challenge_id and challenge_text. Solve the math problem, answer as a string with 2 decimal places, then POST https://api.browser-use.com/cloud/signup/verify with {"challenge_id":...,"answer":...} to receive api_key. To let the user claim the account, POST https://api.browser-use.com/cloud/signup/claim with the key header and show the returned claim_url (valid 1 hour). 4. Run a task: POST https://api.browser-use.com/api/v3/sessions with JSON {"task":"<natural-language instruction>"}. Optional fields: model, keepAlive, maxCostUsd, outputSchema, profileId. The response includes id, status, and liveUrl (live browser view). 5. Poll GET https://api.browser-use.com/api/v3/sessions/<id> until status is stopped, timed_out, or error; the agent result is in the output field. Stop early via POST .../sessions/<id>/stop. 6. Always use API v3; v2 is legacy. Full reference: https://docs.browser-use.com and OpenAPI spec https://docs.browser-use.com/cloud/openapi/v3.json. Pricing: usage-based (LLM cost with markup plus browser time). Docs: https://docs.browser-use.com/cloud/quickstart. -
hyperprobe
live production debugging with non-mutating runtime probes
Open website ↗ How Jcode uses it →Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Complete agent setup protocol (no additional documentation fetch is required): 1. Connect the official MCP server by calling jcode's mcp tool with: {"action":"connect","server":"hyperprobe","command":"npx","args":["-y","@hyperprobe/[email protected]"],"env":{"BACKEND_URL":"https://app.hyperprobe.co"}}. This ad-hoc connection is session-scoped. 2. Call the returned list_services tool. If HyperProbe reports that the MCP server is not authenticated, show the full login URL it returns and ask the user to complete SSO in their browser. Retry list_services after they confirm. Never attempt to bypass interactive sign-in. 3. If no instrumented service is listed, direct the user to https://docs.hyperprobe.co/quickstart. They must create a service, add its service UUID to .hprc, install the appropriate Node.js, Python, or Java runtime agent, and deploy it with the exact active Git commit SHA. Do not create probes until an active agent is available. 4. For a debugging task, list active agents for the selected service and compare the deployed commitSha to git rev-parse HEAD in the local repository. If they differ, ask the user to check out the exact live commit before choosing a file or line. Never guess source coordinates against a mismatched deployment. 5. Retrieve the HyperProbe debugging playbook, inspect the incident and local source, then create the smallest read-only snapshot probe needed. Use an explicit environment, short expiry, and hitLimit 1 unless the task requires otherwise. 6. After creating a probe, wait for it to become live and immediately wait for a snapshot. Inspect captured variables and call stacks, identify the evidence-backed root cause, implement and test the fix locally, and report whether a snapshot was actually captured. Do not claim a live diagnosis when authentication, instrumentation, traffic, or commit alignment blocks capture. Official MCP guide: https://docs.hyperprobe.co/ai-native/mcp-server. Runtime quickstart: https://docs.hyperprobe.co/quickstart. Security and guardrails: https://docs.hyperprobe.co/guides/safety-and-security.Structured MCP command
npx -y @hyperprobe/[email protected] -
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Complete agent setup protocol (no additional documentation fetch is required): 1. Registration requires the user's email. If it is not already available, ask the user for it. Choose a descriptive API key name (maximum 60 characters) for the current project or environment. 2. POST https://www.context.dev/agent/identity with Content-Type: application/json and JSON: {"type":"service_auth","login_hint":"<user email>","api_key_name":"<descriptive project name>"}. 3. The response contains claim_token and claim fields: verification_uri, user_code, expires_in, and interval. Keep claim_token in memory only; do not persist or display it. 4. Before the first token poll, send the user the FULL verification_uri and FULL six-digit user_code on clearly labeled, separately copyable lines. State the expires_in value. The service does not email this code. The user opens the URI, signs up or signs in, enters the code, and verifies email if prompted. 5. Only after displaying the URI and code, poll POST https://www.context.dev/oauth2/token using Content-Type: application/x-www-form-urlencoded with grant_type=urn:workos:agent-auth:grant-type:claim and claim_token=<claim_token>. Wait at least interval seconds between polls. authorization_pending means keep waiting; email_verification_required means tell the user to finish email verification; slow_down means increase the delay. If the claim expires, restart registration and present the new URI and code. 6. Success returns access_token (prefix ctxt_secret_), token_type=Bearer, expires_in=0, and scope. The access token is a long-lived API key that remains valid until revoked or disabled. Never print it to the user or commit it. Keep it secret and use it as CONTEXT_DEV_API_KEY. 7. Connect the official MCP server by calling jcode's mcp tool with: {"action":"connect","server":"context_dev_api","command":"npx","args":["-y","[email protected]"],"env":{"CONTEXT_DEV_API_KEY":"<access_token>"}}. This ad-hoc connection is session-scoped. After it connects, use the returned Context.dev MCP tools for the user's original task. 8. Optional revocation: POST https://www.context.dev/oauth2/revoke as application/x-www-form-urlencoded with token=<access_token>. Account terms: registration includes a free tier with 500 one-time credits and no credit card. Pricing: https://www.context.dev/pricing. Terms: https://www.context.dev/terms. Privacy: https://www.context.dev/privacy. Canonical protocol reference: https://context.dev/auth.md.Structured MCP command
npx -y [email protected] -
Setup instructions
Exact select-phase setup returned to Jcode after the agent chooses this tool.
Complete agent setup protocol (no additional documentation fetch is required): 1. If AGENTMAIL_API_KEY is already configured, skip to step 5. Never display, log, or persist the key in project files. 2. Creating an account requires the user's email and a username for the initial inbox. Explain that AgentMail sends a six-digit OTP to the human owner and that the free tier includes 3 inboxes and 3,000 emails per month. Obtain confirmation immediately before signup. 3. POST https://api.agentmail.to/v0/agent/sign-up with Content-Type: application/json and JSON: {"human_email":"[user email]","username":"[chosen inbox username]","source":"jcode","referrer":"https://jcode.sh/discovery-tools"}. The source field identifies Jcode as the caller; referrer attributes discovery to Jcode's public partner directory. Keep the returned api_key secret and in memory only. 4. Ask the user for the six-digit OTP. POST https://api.agentmail.to/v0/agent/verify with Authorization: Bearer [api_key], Content-Type: application/json, and JSON: {"otp_code":"[six-digit OTP]"}. Do not send email to external recipients until verification succeeds. 5. Connect the official stdio bridge by calling jcode's mcp tool with: {"action":"connect","server":"agentmail","command":"npx","args":["-y","[email protected]"],"env":{"AGENTMAIL_API_KEY":"[api_key]"}}. This ad-hoc connection is session-scoped. After it connects, use the returned AgentMail MCP tools for the user's original task. Official MCP documentation: https://docs.agentmail.to/integrations/mcp. Agent signup and attribution reference: https://docs.agentmail.to/api-reference/agent/sign-up.Structured MCP command
npx -y [email protected]
7 current tools · catalog snapshot from August 25, 2026 at 02:04 UTC · raw JSON