Build solutions, not workarounds.
What do you want Steem and Teambook to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Steem can start in Teambook
When New account history event (poll) in Steem
then Add Actual log in Teambook
When New post (poll) in Steem
then Add Booking in Teambook
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Steem and Teambook
Triggers and actions 2 triggers · 44 actions
Trigger
New account history event (poll)Poll an account's operation history for new on-chain events such as transfers or votes (condenser_api.get_account_history).
Trigger
New post (poll)Poll for newly created posts across the chain or blog, fired for automations reacting to fresh Steem content (condenser_api.get_discussions_by_created).
Action
Find accountsSearch for Steem accounts by name prefix or list (condenser_api.lookup_accounts).
Action
Find trending tagsList the tags currently trending on the Steem blockchain (condenser_api.get_trending_tags).
Action
Get accountLook up a Steem blockchain account's profile, balances, and reputation by username (condenser_api.get_accounts).
Action
Get account historyRetrieve an account's on-chain operation history (transfers, votes, posts) (condenser_api.get_account_history).
Action
Get postRetrieve a single post or comment's content and metadata by author and permlink (condenser_api.get_content).
Action
Get post repliesList the comment replies under a given post (condenser_api.get_content_replies).
Action
List followersList the accounts following a given Steem account (condenser_api.get_followers).
Action
List followingList the accounts a given Steem account follows (condenser_api.get_following).
Action
List posts on an account's blogList the posts and reblogs an account has published to its blog (condenser_api.get_discussions_by_blog).
Action
List trending posts by tagList the current trending discussions, optionally filtered by tag (condenser_api.get_discussions_by_trending).
Action
Add Actual logCreates one or more time-tracking actual logs in a batch.
Action
Add BookingCreates one or more bookings in a batch.
Action
Add ClientCreates a client record.
Action
Add TaskCreates a task, optionally scoped to a project (omit project_id for account-wide task).
Action
Create ProjectCreate a Project inside Teambook
Action
Create UserCreates a teambook User
Action
Deactivate UserDeactivates a Teambook user so they can no longer be booked or sign in, without deleting their history.
Action
Delete Actual logDeletes an actual log by id.
Action
Delete BookingRemoves a single booking from Teambook.
Action
Delete ProjectDeletes a project by id.
Action
Delete TaskDeletes a task from the Teambook account.
Action
Delete UserDeletes a user from the Teambook account.
Action
Get Actual logRetrieve a single Teambook actual log (time entry) by its id.
Action
Get BookingRetrieve a single Teambook booking (a user's assignment to a project on a date for a duration) by its id.
Action
Get ClientRetrieves a single client by id.
Action
Get ProjectRetrieves a single project by id.
Action
Get TaskRetrieves a single task by id.
Action
Get TeamRetrieve a single Teambook team by its id.
Action
Get UserRetrieve a single Teambook user by id.
Action
List Actual logsLists actual logs (timesheet entries), filterable by user_id, project_id, since, range.
Action
List BookingsLists bookings, optionally filtered by team, user, project and date window. Returns the first page of up to 100 bookings.
Action
List ClientsReturns every client in the Teambook account.
Action
List Project capacitiesLists project capacity entries (days reserved per project per month) entered on the Capacity by Project page.
Action
List ProjectsLists all projects in the Teambook account.
Action
List TasksLists all tasks.
Action
List TeamsLists all teams in the Teambook account.
Action
List User capacitiesLists monthly capacity-reservation rows per user, filterable by user_id and since (first day of month).
Action
List UsersLists all users in the Teambook account.
Action
Update Actual logEdits an actual log's project, user, date, duration, task, payroll_item, approved, or comment.
Action
Update BookingUpdates an existing Teambook booking; only the fields you fill in are changed.
Action
Update ClientEdits a client's name, phone_number, or email.
Action
Update ProjectEdits a project's fields (name, code, active, color, kind, estimated, notes, client_id, manager_id, dates, custom_fields).
Action
Update TaskEdits a task's name or project_id.
Action
Update UserEdits a user's first_name, last_name, email, role, billable, time_zone, phone_number, language, or schedule.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Steem
Steem to StripeStripe is a payment processing platform for online businesses.
Steem to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Steem to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Steem to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Steem to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Steem to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Teambook
HubSpot to TeambookHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TeambookSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TeambookSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TeambookGoogle Sheets
Gmail to TeambookGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TeambookGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Steem and Teambook, answered
What can start an automation from Steem?
Any of Steem's 2 triggers in the catalog, including New account history event (poll) and New post (poll). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Teambook when something happens in Steem?
Any of Teambook's 34 actions, including Create Project, Create User, Update Actual log and Update Booking. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Teambook to Steem?
Teambook has no triggers in the catalog today, so automations start in Steem. If you need the other direction, ask: your agent reads Teambook's API documentation and adds it.
Do I have to build a connector for Steem or Teambook?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.