Integration

Connect JOIN to Kitsu

When Application Created fires in JOIN, your agent runs Update anime in Kitsu. Describe the whole flow and it is built, tested on every scenario and kept running.

JOIN3 triggers JOIN16 actions Kitsu9 actions

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 JOIN and Kitsu to do together?

Ask the assistant

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide

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

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

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

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

Example flows

What JOIN can start in Kitsu

When Application Created in JOINthen Update anime in Kitsu
When Job Published in JOINthen Update episode in Kitsu

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 JOIN and Kitsu

Triggers and actions 3 triggers · 25 actions

Trigger
Application Created
Triggers when a new job application is received in JOIN.
Trigger
Job Published
Triggers when a job is published (goes online) in JOIN.
Trigger
Job Unpublished
Triggers when a job is taken offline or archived in JOIN.
Action
Add candidate note
Adds a note to a candidate in JOIN.
Action
Add job
Creates a job in JOIN. New jobs are activated and multiposted to job boards automatically.
Action
Add location
Creates a new office location in JOIN that job ads can be assigned to.
Action
Create Application
Creates an application for a candidate on a JOIN job, optionally attaching documents such as a CV.
Action
Get application
Returns one job application, including its candidate, job, attachments, screening answers and pipeline stage.
Action
Get candidate
Returns a single JOIN candidate by id, including contact details, tags, consent status and their applications, with notes optionally embedded.
Action
Get job
Returns a single JOIN job by its ID, including its title, status, office and optionally its full content.
Action
Get Jobs
Returns jobs in your JOIN account, optionally filtered by status, title, country, external id, or creation/update dates.
Action
Get Online Jobs
Returns the jobs currently published (online) in your JOIN account, optionally filtered by title, country, dates or external id.
Action
List applications
Returns the applications in your JOIN account, optionally filtered by job, dates, country, hiring state or pipeline stage.
Action
List candidate notes
Returns all notes recorded on a candidate in JOIN, including replies.
Action
List candidates
Returns the candidates in your JOIN company, optionally filtered by a name/email search or creation date.
Action
List candidate scorecards
Returns the scorecards submitted for a candidate's job application, including each interviewer's overall recommendation, attribute ratings and question answers.
Action
List locations
Returns the office locations in your JOIN account, optionally filtered by country or city.
Action
Update job
Updates an existing job's details, such as title, description, office, salary, and application requirements. Fields you leave blank stay unchanged.
Action
Update Job Status
Changes a JOIN job's status to online, offline or archived, and returns the job's ID.
Action
Get anime
Returns a single anime from Kitsu by its id, including titles, synopsis, ratings, dates, episode details and images.
Action
Get episode
Returns a single Kitsu episode by its id, including titles, season and episode numbers, synopsis and airdate.
Action
Get manga
Returns a single manga from Kitsu by its id, including titles, synopsis, ratings and chapter details.
Action
List anime
Returns a list of anime from Kitsu, optionally filtered by search text, category, season, year, streamer or age rating.
Action
List episodes
Returns Kitsu episodes, optionally filtered by anime and episode number.
Action
List manga
Returns manga from the Kitsu catalog, optionally filtered by search text, category or chapter count and sorted.
Action
Update anime
Updates an existing anime's details on Kitsu. Requires an admin account.
Action
Update episode
Updates an existing episode's titles, numbering, synopsis, air date, length or thumbnail. Requires an admin account.
Action
Update manga
Updates an existing manga's details on Kitsu, such as its titles, synopsis, dates, status and chapter counts. Requires an admin account.

Each app on its own

Reviews

What our customers say

More into Kitsu

Questions

JOIN and Kitsu, answered

What can start an automation from JOIN?

Any of JOIN's 3 triggers in the catalog, including Application Created, Job Published and Job Unpublished. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Kitsu when something happens in JOIN?

Any of Kitsu's 9 actions, including Update anime, Update episode, Update manga and Get anime. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Kitsu to JOIN?

Kitsu has no triggers in the catalog today, so automations start in JOIN. If you need the other direction, ask: your agent reads Kitsu's API documentation and adds it.

Do I have to build a connector for JOIN or Kitsu?

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 JOIN and Kitsu 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.

Connect JOIN to Kitsu

What do you want JOIN and Kitsu to do together?

What JOIN can start in Kitsu

Triggers and actions 3 triggers · 25 actions

Each app on its own

What our customers say

More from JOIN

More into Kitsu

JOIN and Kitsu, answered

What can start an automation from JOIN?

What can your agent do in Kitsu when something happens in JOIN?

Can it also run from Kitsu to JOIN?

Do I have to build a connector for JOIN or Kitsu?

Can my AI client use JOIN and Kitsu without building an automation?

What happens when something fails?

Is there a free plan?