llms.txt Content
# Stumpy
> Agent platform at stumpy.ai. You push a button, get an agent, tell it what to do, and it plugs into your calendar, email, Slack, and other services. Agents live in the cloud and you interact with them wherever you are. Make one your personal assistant, or spin up a team and have them run parts of your business.
You configure agents through conversation, not workflow builders. Tell an agent what you want it to do and it adapts. Each agent has persistent memory, file storage, and can connect to external services.
The platform is hosted at stumpy.ai. There is no self-hosted option.
## Core Concepts
Agents: Each agent is an independent AI assistant with its own identity, memory, enabled plugins, and file storage. Agents are single-threaded—they process one task at a time.
Identity: A persistent system prompt that defines the agent's personality and purpose. Users shape it through conversation ("remember that you're a customer support agent"); the agent updates its own identity file in response. The identity lives at `.stumpy/identity.md` and can also be edited directly via the Files tab.
Plugins: Modular capability packs. Each plugin provides tools (actions the agent can take), hooks (triggers like webhooks or cron), and configuration. Agents can enable/disable plugins and modify plugin config through conversation.
App Connections: Pre-configured MCP server integrations from a curated catalog. Users connect external services (like Stripe, Monday.com, Attio, PayPal, Sentry, Todoist, Linear, Dropbox, Canva, Webflow, and 15+ more) with one click, without needing to know MCP details. App connections appear alongside plugins in the agent's connections list and provide tools with the same mcp__{name}__{tool} naming pattern as custom MCP servers.
Context: Agents maintain conversation history with automatic compaction when approaching token limits. Important information persists through the identity system.
## Agent Capabilities
All agents have these cap