productivityapi_key

Moco

MOCO is a business management software offering project management, time tracking, and invoicing solutions.

Verdict

Moco is a time-tracking and project management platform for agencies and consultancies. In Switchy, @mentioning Moco lets your team create projects, log hours, generate invoices, and manage client records without leaving the conversation. Project managers can spin up new engagements, designers can log billable time to the right project code, and finance can draft invoices from tracked hours — all by asking the AI. You'll need a Moco API key with read-write permissions. Moco doesn't expose reporting endpoints via MCP, so you can't pull analytics or dashboards directly.

Common use cases

  • Log billable hours to client projects from chat
  • Create invoices from tracked time without switching apps
  • Spin up new projects and assign team capacity
  • Add client companies and contacts on the fly
  • Record expenses and purchases during team sync

Integration

Vendor
Moco
Category
productivity
Auth
API_KEY
Tools
25
Composio slug
moco

Tools

  • Create Company

    Tool to create a new company. use when you need to add a company after gathering required fields.

  • Create Invoice

    Tool to create a new invoice. use after gathering complete invoice data (customer, dates, items, etc.).

  • Create Planning Entry

    Tool to create a new planning entry. use when you need to allocate working hours to a project or deal.

  • Create Project

    Tool to create a new project in moco. use when you need to provision a project with validated parameters.

  • Create Purchase

    Tool to create a new purchase. use when you need to log an expense record after gathering date, items, and payment info.

  • Delete a company
    destructive

    Tool to delete a company. use when you need to remove a company from moco after confirming no active dependencies.

  • Delete Deal
    destructive

    Tool to delete a deal. use when you have identified an obsolete or unwanted deal and confirmed its deletion. example: "delete the deal with id 123."

  • Get Activity

    Tool to retrieve a single activity by id. use when you need to fetch details for a specific activity after confirming the activity id.

  • Get Deal

    Tool to retrieve a single deal by id. use when you have a deal id and need detailed deal information. use after confirming the deal id.

  • Get Offer

    Tool to retrieve a single offer by id. use when you have an offer id and need detailed offer information. use after confirming the offer id.

  • Get Planning Entry

    Tool to retrieve a single planning entry by id. use when you need detailed information for a specific planning entry after confirming its id.

  • Get Project

    Tool to retrieve a single project by id. use when you need detailed project information after confirming the project id.

  • List Activities

    Tool to retrieve activities. use when you need to list time entries with filters like date range, user, project, or billing status.

  • List comments

    Tool to retrieve a list of comments. use after confirming the resource type and id.

  • List Contacts

    Tool to retrieve a list of contacts. use when you need to list contacts optionally filtered by tags, term, or phone after confirming criteria.

  • List Deal Categories

    Tool to list deal categories with their ids and probabilities. use when you need a reference of available deal category types after authenticating.

  • List Deals

    Tool to retrieve a list of all deals (leads). use when you need an overview of deals filtered by status, tags, date range, or associated company.

  • List Invoices

    Tool to retrieve a list of all invoices. use when you need an overview of invoices, optionally filtered by status, date range, or client.

  • List Offers

    Tool to retrieve a list of all offers. use when you need an overview of offers filtered by status, date range, or identifiers.

  • List Planning Entries

    Tool to retrieve a list of all planning entries. use when you need an overview of planned hours filtered by period, user, or project.

  • List Projects

    Tool to retrieve a list of all projects. use when you need an overview of projects optionally filtered by company, leader, date range, or tags after confirming criteria.

  • List Users

    Tool to list all users. use when you need valid 'leader id' or 'co leader id' for project creation after confirming available staff.

  • Update Activity

    Tool to update an existing activity. use when you need to adjust details of a recorded time entry after confirming the activity exists.

  • Update Deal

    Tool to update an existing deal. use when you need to modify one or more fields of a deal after retrieving its details.

  • Update Project

    Tool to update an existing project. use when you need to modify project details after confirming the project id.

Setup

Setup guide

  1. 11. In Switchy, open the Space where you want Moco available and click Integrations in the sidebar. 2. Search for Moco and click Connect. 3. You'll be prompted for your Moco API key — generate one by logging into your Moco account, navigating to Settings > Integrations > API, and creating a new key with read and write scopes. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection and shows which tools are now available. 6. Test it by typing '@Moco list my active projects' in the Space — the AI should return your current project roster. 7. From now on, any message that @mentions Moco will let the AI invoke tools like creating invoices, logging planning entries, or adding new companies.

What teammates see: by default, memories from Moco are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Log Time to Project

@Moco create a planning entry for 4 hours today on project PRJ-204, task 'Design review'. Mark it billable.
Open in a Space →

Draft Client Invoice

@Moco create an invoice for Acme Corp covering all unbilled hours in March. Use net-30 terms and include the retainer discount.
Open in a Space →

Start New Project

@Moco create a project called 'Brand Refresh' for client ID 88, budget 40k, start date May 1, fixed-price billing.
Open in a Space →

Add Client Company

@Moco add a new company named 'Vertex Labs', industry Software, billing address 123 Main St, contact email billing@vertex.io.
Open in a Space →

Record Team Expense

@Moco create a purchase for project PRJ-204, date today, amount 250 USD, category 'Software licenses', paid by company card.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Moco show me all planning entries for the 'Website Redesign' project this week and summarize who's allocated where

Output

Based on the planning entries retrieved from Moco, here's the allocation for 'Website Redesign' this week: Sarah Chen is scheduled for 16 hours across Monday-Wednesday focusing on frontend development. Marcus Liu has 12 hours Thursday-Friday for backend API work. The project currently shows 28 of 40 planned hours allocated, leaving capacity for additional assignments. All entries are confirmed and no scheduling conflicts were detected.

Notes

This example demonstrates Moco's read capabilities for resource planning. The MCP can fetch planning entries filtered by project and date range, then the AI synthesizes the data into actionable insights. Requires read access to planning entries; actual output structure depends on your team's planning entry fields and project naming conventions.

Prompt

@Moco create a new project called 'Q2 Brand Refresh' for Acme Corp, budget 50000 EUR, starting April 1st with a 12-week timeline

Output

I've created the project 'Q2 Brand Refresh' in Moco with the following details: Customer set to Acme Corp, budget €50,000, start date April 1, 2025, estimated end date June 24, 2025. The project has been assigned ID #4782 and is now active in your workspace. You can begin adding tasks, assigning team members, and creating planning entries against this project immediately.

Notes

This showcases Moco's project creation workflow, a core write operation for agencies and consultancies. The MCP handles the API call after gathering required fields. Note that you'll need write permissions for projects, and the customer (Acme Corp) must already exist in your Moco account—the MCP will error if it can't resolve the customer reference.

Prompt

@Moco pull all invoices from last month that are still unpaid and draft a follow-up email template I can send to those clients

Output

I found 4 unpaid invoices from March 2025 totaling €23,400: Invoice #1847 to Beta Industries (€8,200, due March 15), #1851 to Zenith Partners (€6,500, due March 22), #1856 to Acme Corp (€5,200, due March 28), and #1859 to Startup Labs (€3,500, due March 30). Here's a professional follow-up template: 'Hi [Client Name], I hope this message finds you well. I wanted to follow up on Invoice #[Number] for €[Amount], which was due on [Date]. If payment has already been sent, please disregard this message. Otherwise, could you confirm the expected payment timeline? Let me know if you need a copy of the invoice or have any questions. Best regards.'

Notes

This example combines Moco's invoice retrieval with AI-powered synthesis—perfect for accounts receivable workflows. The MCP fetches invoice data filtered by date and payment status, then the AI generates contextual output. Be aware that invoice queries can return large datasets for busy agencies; consider narrowing the date range if you hit rate limits or timeouts.

Use-case deep-dives

Agency project kickoff automation

When Moco wins for spinning up client projects fast

A 6-person creative agency closes a new client deal and needs to create the company record, provision the project, and allocate the first sprint's hours—all before the kickoff call ends. Moco's MCP handles this in one conversation: you create the company, wire up the project with budget and billing terms, then drop planning entries for the designer and copywriter. The auth is a single API key, so onboarding takes five minutes. This works when your project structure is stable (same phases, same roles) and you're doing 3-8 new projects a month. If you're spinning up 40 projects a quarter or your billing logic changes per client, you'll want a dedicated onboarding script instead. For small agencies with repeatable project templates, Moco's MCP turns kickoff admin from 20 minutes of clicking to one 90-second chat.

Expense logging for remote consultants

When this MCP simplifies purchase tracking at scale

A 12-person consulting firm has contractors filing expenses from three time zones—coffee with a prospect, a SaaS subscription, travel to a client site. The finance lead used to chase people for receipts in Slack, then manually enter purchases in Moco. Now contractors describe the expense in chat (date, vendor, amount, category) and the MCP writes the purchase record directly. The 25-tool scope includes invoice and project creation, so the same workspace handles billing workflows without switching contexts. This breaks down if your expense policy requires multi-level approval or you're integrating with a separate ERP—Moco's purchase tool is a flat create, no workflow engine. For firms under 20 people with straightforward expense rules, the MCP cuts the finance lead's weekly admin from 90 minutes to 15.

Deal pipeline cleanup for sales ops

When Moco's MCP handles CRM hygiene without a script

A 4-person SaaS startup tracks inbound leads as Moco deals, but the pipeline fills with stale opportunities—old demos that ghosted, pricing calls that went cold. The sales ops person used to click through the web UI every Friday to archive dead deals. With the MCP, they ask "show me deals older than 60 days with no activity, then delete the ones marked lost" and the workspace fetches activities, filters by date, and runs the delete tool in a loop. The 25-tool kit includes company and project management, so the same integration prunes obsolete client records when contracts end. This only works if your deal volume is under 200 active opportunities—beyond that, the MCP's per-record API calls get slow and you need a bulk-delete endpoint. For early-stage teams doing manual CRM grooming, Moco's MCP turns Friday cleanup from 30 minutes of clicking to one question.

Frequently asked

What does the Moco MCP let me do in Switchy?

It connects your Moco account so AI agents can create and manage companies, projects, invoices, purchases, planning entries, and deals directly from chat. You can ask an agent to log a client expense, spin up a new project with tasks, or pull activity details without opening Moco's UI. All 25 tools run through Moco's API, so changes sync instantly.

Do I need admin access to connect Moco?

You need a Moco API key, which typically requires account admin or owner permissions to generate. Standard users can't create API keys in most Moco plans. Once connected, the MCP inherits the permissions of that API key—if the key can delete companies or invoices, so can the agent.

Can the Moco MCP edit existing invoices or projects?

The representative tools show create and delete actions, but no explicit update endpoints. If Moco's API supports PATCH or PUT for invoices and projects, those tools may exist in the full 25-tool set. Check the MCP's complete tool list in Switchy or ask the agent to try updating a record; it will tell you if the operation isn't available.

Why use this instead of logging into Moco directly?

Speed and context. An agent can create a project, add planning entries, and draft an invoice in one conversation, pulling data from Slack threads or Google Docs you reference. You skip five browser tabs and manual copy-paste. For bulk operations—like importing ten deals from a spreadsheet—the MCP is dramatically faster than Moco's web forms.

Who on the team should connect the Moco integration?

Whoever owns your Moco API keys—usually a finance lead, project manager, or account admin. That person's API key determines what the agent can read and write. If multiple people need Moco access in Switchy, each can connect their own key, or you can share one key and accept that all actions appear under that user in Moco's audit log.

Data last verified 608 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.