{
  "markdown": "# tau\n\n[![npm version](https://img.shields.io/npm/v/taufunctions.svg)](https://www.npmjs.com/package/taufunctions)\n[![MCP](https://img.shields.io/badge/MCP-12_tools-blue)](#mcp-server)\n[![Runtimes](https://img.shields.io/badge/runtimes-node%20%C2%B7%20python%20%C2%B7%20go%20%C2%B7%20ruby%20%C2%B7%20rust-f97316)](#runtimes)\n\n**Serverless functions for coding agents — deploy, invoke, and monitor from one CLI. As easy as git.**\n\n> **git for your code. tau for your functions.**\n\nYour agent writes a webhook handler, a cron job, a data transform — then hits a wall: AWS consoles, IAM policies, YAML, a deploy pipeline it can't drive. So *you* become the middleman, clicking through Lambda screens for code you didn't write. TauFunctions is the serverless platform your agent runs itself: one install, and it creates, deploys, invokes, and monitors its own functions — from the terminal, with plain JSON in and out.\n\n**Works with:** Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any MCP client\n\n[![tau demo — create to invoked function in 60 seconds](https://prodmedia.tyga.host/public/tyga.cloud/landing/taufunctions.com/tau-demo-1200.gif)](https://taufunctions.com/#demo)\n\n*Create to invoked function in 60 seconds — [watch the full demo](https://taufunctions.com/#demo).*\n\n## Install\n\n```bash\nnpm install -g taufunctions\n```\n\nThe npm package is `taufunctions`; the command is `tau`.\n\n## Quick Start\n\n```bash\n# Sign up\ntau signup you@example.com --tenant my-project\n\n# Create a function from a file\ntau fn create \"process-order\" -r nodejs20 --file handler.js\n\n# Deploy it\ntau deploy <function-id>\n\n# Invoke with a JSON payload\ntau invoke <function-id> '{\"orderId\": \"ORD-001\"}'\n\n# Watch it run\ntau logs <function-id>\ntau stats <function-id>\n\n# Full reference\ntau --help\n```\n\n## No consoles, no YAML, no IAM maze\n\nA function on TauFunctions is exactly what your agent already has in its context: a handler file and a runtime. No zip bundles, no execution roles, no API Gateway wiring, no infrastructure-as-code detour just to run 20 lines of JavaScript.\n\n```bash\n# The whole deploy story:\ntau fn create \"resize-image\" -r nodejs20 --file resize.js\ntau deploy $FN\ntau invoke $FN '{\"url\": \"https://example.com/photo.jpg\", \"width\": 800}'\n```\n\nCreate → deploy → invoke is three commands, and every one returns structured output your agent can parse with `--json`.\n\n## Iterate like you're editing a local file\n\nShipping v2 doesn't mean a new pipeline run. Push new code at an existing function and redeploy — the function ID, URL, and history stay put.\n\n```bash\ntau fn code $FN --file hello.js      # swap in the new handler\ntau deploy $FN                       # redeploy\ntau invoke $FN '{\"version\": 2}'      # verify\n```\n\n## Monitor everything from the terminal\n\nNo CloudWatch spelunking. Invocation counts, durations, error rates, and execution logs are one command each — formatted for humans, `--json` for agents.\n\n```bash\ntau stats $FN            # invocations, avg duration, error rate\ntau logs $FN --tail 20   # recent executions\ntau limits               # your plan's quotas and current usage\n```\n\n## Runtimes\n\n```bash\ntau runtimes\n```\n\nNode.js 18/20/22, Python 3.11/3.12, Go 1.21/1.22, Ruby 3.2, and Rust 1.75. Node.js functions execute today on auto-scaling Docker Swarm containers; the remaining runtimes are rolling out on the same executor.\n\n## MCP Server\n\nPrefer tools over a CLI? `tau` ships an MCP server. Point Claude Code (or any MCP client) at it and your agent gets **12 native tools**: create, deploy, invoke, update, delete, logs, stats, runtimes, limits, health — the whole function lifecycle.\n\n```bash\nclaude mcp add taufunctions -- tau mcp-serve\n```\n\nFor clients that use a JSON config (Cline, Cursor, Windsurf), pass your API key via the `TAU_API_KEY` environment variable. The MCP server runs outside your project directory, so it will not pick up `.tau/config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"taufunctions\": {\n      \"command\": \"tau\",\n      \"args\": [\"mcp-serve\"],\n      \"env\": { \"TAU_API_KEY\": \"tf_your_key_here\" }\n    }\n  }\n}\n```\n\n### Remote MCP — zero install\n\nNo CLI at all? Claude Web, Claude Desktop, Raycast, or any hosted MCP client can connect straight to our remote server. Same 13 tools, same API key, nothing to install:\n\n```\nURL:  https://mcp.taufunctions.com/sse\nAuth: Authorization: Bearer YOUR_API_KEY\n```\n\nNo key yet? Connect without one — the server boots in onboarding mode with a `tau_signup` tool that provisions your account and hands your agent a live key in the same session.\n\n## Features\n\n- **Functions** — create, deploy, invoke, update, delete; JSON payload from CLI or file\n- **Runtimes** — Node.js, Python, Go, Ruby, Rust\n- **Deploy** — one command to auto-scaling Docker Swarm, no pipeline\n- **Logs & stats** — execution logs, invocation counts, durations, error rates\n- **Limits** — plan quotas and live usage from the terminal\n- **MCP server** — 13 tools, local (`tau mcp-serve`) or fully remote (`mcp.taufunctions.com`): Claude Code, Claude Web, Cursor, Raycast, any MCP client\n- **Agent-first output** — every command takes `--json` for structured, parseable results\n\n**Pricing:** per-invocation billing, no idle cost. [Details](https://taufunctions.com/#pricing).\n\n## Per-Project Config\n\n```bash\ntau login --key YOUR_KEY             # saves to .tau/config.json (project-local)\ntau login --key YOUR_KEY --global    # saves to ~/.tau/config.json (global)\ntau config                           # show which config is active\n```\n\nLocal config overrides global. Add `.tau/` to your `.gitignore`.\n\n## Agent Integration\n\nAdd to your CLAUDE.md, .cursorrules, .clinerules, .windsurfrules, or AGENTS.md:\n\n```\n## TauFunctions\nUse the tau CLI for serverless function management.\nKey is in .tau/config.json (auto-loaded).\nIf not configured: tau login --key YOUR_KEY\nRun tau --help for the full command reference.\n```\n\n## Why this exists\n\nEvery time my agent needed \"just a small endpoint,\" the answer was a detour through cloud consoles it couldn't drive — so I ended up clicking through deploy screens for code I didn't write. TauFunctions is the serverless platform the agent runs itself. It's early and I'm iterating fast: if something's rough or missing, [tell me](https://taufunctions.com) — I read everything.\n\n## Documentation\n\n- [Quickstart Guides](https://taufunctions.com/docs/quickstart.html)\n- [Full Reference](https://taufunctions.com/docs/llms.txt)\n\n## License\n\nProprietary - Tyga.Cloud Ltd. See [LICENSE](./LICENSE).\n",
  "bytes": 6493,
  "sha": "cafa37e81823679754ea182e70430ae9966acc972df49c7814cbbc8427d05906",
  "repo_slug": "jyswee/taufunctions",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_jyswee_taufunctions_666b6f27/readme"
}