Ambee Automation via Rube MCP
SkillSearchOnce this skill is added, your AI can fetch environmental data from Ambee, such as air quality and pollen information. The skill handles the Ambee side of the work, so you can simply ask for these details in a normal conversation. It covers Ambee environmental data tasks generally, with air quality and pollen as the main examples.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, ask your AI for the environmental data you need, for example air quality or pollen levels. If a request doesn't work as expected, ask it to check which Ambee actions it has available first.
Then ask your AI: use the Ambee Automation via Rube MCP skill
What your AI can do with it
- Fetch air quality information
- Look up pollen information
- Automate Ambee environmental data tasks
- Check which Ambee actions are available before using them
What this skill tells your AI
The instructions your AI receives, as published by composiohq/awesome-claude-skills in composio-skills/ambee-automation/SKILL.md and read by ahel’s review.
Automate Ambee operations through Composio's Ambee toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/ambee
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ambee connection via
RUBE_MANAGE_CONNECTIONSwith toolkitambee - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitambee - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Ambee operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Ambee task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["ambee"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Ambee-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit ambee |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Signals
- GitHub stars
- 75k
- Forks
- 9k
- Last commit
- Aug 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
ambee-automation-composiohq- Source
- github.com/composiohq/awesome-claude-skills