agentleFS
developerz-aideveloperz-ai/mcp-ssh/.claude/skills/mcp-token/SKILL.md

mcp-token

Skill2 starsChanged 2 days agoMITView on GitHub

Mint an OAuth bearer for headless MCP clients against a running server. Use for mcp-token, bearer, headless, claude cli, auth, pkce

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start the server locally: MCP_SSH_USER=<dev-user> MCP_SSH_PASS=<dev-pass> MCP_SSH_DB="$PWD/.local/mcp-ssh.db" …

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

House skill — established by the developerz.ai maintainer agent for the maintainers of this repository from this repo's own evidence, then owned by its maintainers. Correct it in place; setup never overwrites a skill that exists.

  1. Start the server locally: MCP_SSH_USER=<dev-user> MCP_SSH_PASS=<dev-pass> MCP_SSH_DB="$PWD/.local/mcp-ssh.db" MCP_SSH_JOB_DIR="$PWD/.local/jobs" bin/dev (binds 127.0.0.1:1337; no root dirs needed).
  2. Verify up: curl -fsS http://127.0.0.1:1337/.well-known/oauth-authorization-server.
  3. Mint the bearer: bin/mcp-token (reads MCP_SSH_USER/MCP_SSH_PASS from .env or the environment; set MCP_SSH_URL to target a non-local server).
  4. Hand it to a headless client: claude mcp add --transport http mcp-ssh http://localhost:1337/mcp --header "Authorization: Bearer $(bin/mcp-token)". fail -> "client registration failed (server down?)" or "no consent form from /authorize" means the server is not up; "login refused (HTTP 401)" means wrong MCP_SSH_USER/MCP_SSH_PASS. The access token lasts 24h and survives server restarts (stored hashed in SQLite); re-run after it expires, or after mcp-ssh sessions --revoke / set-auth. Never echo the token into logs or commits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.