App

wethod integrations

Connect wethod to any other app, or use it from your AI client over MCP. wethod is project management software that helps teams and companies to plan work, track budgets, and monitor project profitability.

Connects with an API keywethod.com

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 to automate with wethod?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

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 (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)
Grok

Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.

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)

Pair it

Connect wethod with another app

What your agent can do with wethod

Triggers and actions 7 triggers · 50 actions

  • Trigger
    New Client

    Required permissions: - **crm.view**: allows view all resources. Here the dedicated support page.

  • Trigger
    New Contact

    Required permissions: - **crm.view**: allows view resources. Here the dedicated support page.

  • Trigger
    New Invoice

    Required permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.

  • Trigger
    New Person

    Here the dedicated support page.

  • Trigger
    New Project

    This endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the

  • Trigger
    Sent Invoice

    Triggers when an invoice is in sent status.

  • Trigger
    Updated Project

    Triggers when a project is created or updated.

  • Action
    Archive a project

    Required permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.

  • Action
    Create a client

    Required permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.

  • Action
    Create a contact

    Required permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.

  • Action
    Create an invoice

    Required permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.

  • Action
    Create a person

    Creates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/

  • Action
    Create a person allocation

    Required permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He

  • Action
    Create a project

    Required permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met

  • Action
    Create a project status

    Required permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.

  • Action
    Create a timesheet

    Required permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.

  • Action
    Delete a client

    Required permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.

  • Action
    Delete a contact

    Required permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.

  • Action
    Delete an invoice

    Required permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.

  • Action
    Delete a person allocation

    Required permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He

  • Action
    Delete a project

    Required permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.

  • Action
    Delete a timesheet

    Required permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.

  • Action
    Find Client

    Finds the first client whose name matches the search text.

  • Action
    Find Person

    Finds the first person whose name or email matches the search text.

  • Action
    Get a budget

    Required permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.

  • Action
    Get a client

    Required permissions: - **crm.view**: allows view all resources. Here the dedicated support page.

  • Action
    Get a contact

    Required permissions: - **crm.view**: allows view resources. Here the dedicated support page.

  • Action
    Get an expense

    Required permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.

  • Action
    Get an invoice

    Required permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.

  • Action
    Get a person

    Here the dedicated support page.

  • Action
    Get a project

    This endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the

  • Action
    Get a stream

    :::warning Requires **Streams** to be enabled in company settings. :::

  • Action
    Get the authenticated person

    Returns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.

  • Action
    List budgets

    Required permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.

  • Action
    List business units

    Required permissions: - **settings.company**: allows view of company business units.

  • Action
    List clients

    Required permissions: - **crm.view**: allows view all resources. Here the dedicated support page.

  • Action
    List contacts

    Required permissions: - **crm.view**: allows view resources. Here the dedicated support page.

  • Action
    List expenses

    Required permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.

  • Action
    List invoices

    Required permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.

  • Action
    List job titles

    Required permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.

  • Action
    List people allocations

    Required permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.

  • Action
    List persons

    Here the dedicated support page.

  • Action
    List projects

    This endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the

  • Action
    List project statuses

    Required permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.

  • Action
    List project types

    List project types

  • Action
    List streams

    :::warning Requires **Streams** to be enabled in company settings. :::

  • Action
    List timesheets

    Required permissions: - **timetracking.view** Here the dedicated support page.

  • Action
    Set an invoice as paid

    Required permissions: - **invoices.edit_sent**: allows setting invoices as paid.

  • Action
    Set an invoice as unpaid

    Required permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.

  • Action
    Unarchive a project

    Required permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.

  • Action
    Update a client

    Required permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.

  • Action
    Update a contact

    Required permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.

  • Action
    Update an invoice

    Required permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.

  • Action
    Update a person

    Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.

  • Action
    Update a person allocation

    Required permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He

  • Action
    Update a project

    Required permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].

  • Action
    Update a timesheet

    Required permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.

Reviews

What our customers say

Questions

wethod, answered

Is there a wethod MCP server?

APIANT's MCP server at https://mcp.apiant.ai works with wethod. Add that address to any AI client that takes a remote MCP server and sign in once in your browser. Your client can then run wethod actions on demand, or have APIANT build, test and run automations that use wethod. Nothing to install.

What can start an automation from wethod?

Any of wethod's 7 triggers in the catalog, including New Client, New Contact, New Invoice and New Person. Describe the moment in plain language and your agent picks the right one.

What can your agent do in wethod?

Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.

Can I use wethod directly from Claude, ChatGPT or Cursor?

Yes. Connect your AI client to APIANT once and it works with wethod two ways. Ask it to do something in wethod 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 on its own. A one-off action uses your plan's tasks the same way an automation step does.

Do I need to write code against the wethod API?

No. APIANT connects to the wethod API for you, with your wethod API key. Describe what you want in plain language and your agent builds it on the wethod triggers and actions in the catalog. If you need an endpoint that is not there yet, your agent reads the wethod API documentation and adds it.

Which apps can wethod connect to?

Any app in the catalog; the list on this page pairs wethod with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

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.