Claude integrations you can keep using across agents
Start in Claude, then use what you built from your other agents, too. Kody keeps your saved tools, accounts, and preferences in one place.
Connect Claude to Kody ↗Find the right connection ↓Save this weekly report workflow in Kody so I can use it again.
Create a reusable package
Each agent connects to the same Kody account.
Your Kody account- Package
- weekly-reportSaved instructions and code
- Memory
- Report preferencesPreferences you’ve saved
- Connection
- Your service accountAccess to the service
Your chats stay in the app where you had them. Your other agents can use the tools and context you save in Kody.
What are you connecting?
Connect your accounts, bring your MCP tools, and keep the workflows you build in Kody.
Kody
Connect your agents to the same Kody account. Keep useful behavior in packages, personal context in memory, and service connections in one place.
Connect the service separately, then test the specific operation you need.
Connect to Kody ↗Two connections.
One useful test.
Connect Claude to Kody
This gives your agent access to your Kody account. Follow the guide for the client you use.
Agent connection guide ↗Connect the service to Kody
A Google or Slack connection supplies that service’s authentication. Connecting Claude alone doesn’t grant it access to your inbox.
How integrations fit together ↗Read something small, then save what helps
Try a task that reads data, check that it’s using the right account, then save useful code as a package or a preference as memory. Ask a second agent to find what you saved.
What carries between agents ↗
Help me connect Claude to my Kody account using the appropriate client guide. Then help me choose one read-only task to test. Explain which service connection it needs and what, if anything, should be saved as a package or memory.