Integration
Connect Bitbucket to Tempo
When New pull request fires in Bitbucket, your agent runs Add customer in Tempo. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Bitbucket and Tempo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Bitbucket tells you when code review work starts; Tempo holds the plans, projects and worklogs that say who has time for it. Connecting the two means a new pull request in Bitbucket can look up the right Tempo project, check a reviewer's schedule, book review time and log it, without anyone retyping issue keys.
Example flows
What Bitbucket can start in Tempo
When New pull request in Bitbucket
then Add customer in Tempo
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 Bitbucket and Tempo
Triggers and actions 1 trigger · 27 actions
- New pull request
- Add branch
/2.0/repositories/{workspace}/{repo_slug}/refs/branches
- Add pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests
- Add pull request comment
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}/comments
- Add repository
/2.0/repositories/{workspace}/{repo_slug}
- Get pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
- List branches
/2.0/repositories/{workspace}/{repo_slug}/refs/branches
- List pull requests
/2.0/repositories/{workspace}/{repo_slug}/pullrequests
- List repositories
/2.0/repositories/{workspace}
- Update pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
- Add customer
Create a customer.
- Add plan
Create a plan (resource allocation).
- Add project
Create a project.
- Add team
Create a team.
- Add worklog
Create a worklog.
- Delete plan
Delete a plan.
- Delete worklog
Delete a worklog.
- Find worklogs by criteria
Search worklogs by issue, project, author, dates.
- Get account
Retrieve an account.
- Get plan
Retrieve a plan by id.
- Get project
Get a project.
- Get user schedule
Retrieve a user's schedule.
- List customers
List customers.
- List plans
List plans.
- List projects
List all projects (Tempo Financial Manager).
- List roles
List roles.
- List teams
List teams.
- Update plan
Update a plan.
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 Bitbucket
Bitbucket to VercelVercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.
Bitbucket to change.photoschange.photos is an API for streamlined image transformations - resize, compress, sharpen, blur, and rotate...
Bitbucket to Football ChartsTables, results, model probabilities and Monte Carlo season projections for 93 leagues
Bitbucket to FruityviceFruityvice is a reference service for fruit data including botanical classification and nutrition.
Bitbucket to Geneea Natural Language Processing
Bitbucket to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Tempo
Salesforce to TempoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TempoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TempoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TempoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TempoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Bitbucket and Tempo, answered
What starts a run between Bitbucket and Tempo?
The one event used here is a new pull request in Bitbucket, which can carry the repository, branch, author and issue key into Tempo. Tempo has no trigger of its own, so runs begin on the Bitbucket side and then read or write Tempo projects, plans and worklogs.
Can the agent check a reviewer's availability before booking time?
Yes, it can retrieve a user's schedule in Tempo and only add a plan when there is free time that week. It can also list existing plans or find worklogs by issue, project or author first, so you are not booking review time twice.
What can start an automation from Bitbucket?
Any of Bitbucket's 1 trigger in the catalog, including New pull request. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Tempo when something happens in Bitbucket?
Any of Tempo's 18 actions, including Add worklog, Find worklogs by criteria, Get account and Get project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tempo to Bitbucket?
Tempo has no triggers in the catalog today, so automations start in Bitbucket. If you need the other direction, ask: your agent reads Tempo's API documentation and adds it.
Do I have to build a connector for Bitbucket or Tempo?
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.
Can my AI client use Bitbucket and Tempo without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.