Integration
Connect awork to Minor Planet Center
When something happens in awork, your agent does the next thing in Minor Planet Center. Describe it 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 awork and Minor Planet Center 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 awork can start in Minor Planet Center
When New Client in awork
then Find MPECs in Minor Planet Center
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 awork and Minor Planet Center
Triggers and actions 8 triggers · 32 actions
- New Client
Fires when a new company/client is created in awork. Poll/webhook on companies resource creation event.
- New Project
Triggers when a new project is created.
- New Task
Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.
- New Time Entry
Triggers when a new time entry is created.
- Updated Client
Fires when an existing company/client is updated in awork. Poll/webhook on companies resource update event.
- Updated Project
Fires when a project is updated in the awork workspace.
- Updated Task
Triggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.
- Updated Time Entry
Triggers when a time entry is updated.
- Create Client
Creates a client (company) in awork and returns the created company.
- Create Project
Creates a new project.
- Create Project Task
Creates a task in an awork project.
- Create Time Entry
Creates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc.
- Delete Client
Deletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks.
- Delete Project
Deletes an awork project and its tasks, optionally deleting its time entries too.
- Delete Project Task
Deletes an awork task by id.
- Delete Time Entry
Deletes a time entry in awork.
- Find Project Tasks by criteria
Returns up to 100 tasks of a project that match the specified filter criteria.
- Find Time Entries by criteria
Returns up to 100 time entries in the workspace that match the specified filter criteria.
- Get Client by ID
Finds a client by id
- Get Project by ID
Finds a project by id
- Get Task by ID
Returns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values.
- Get Time Entry
Returns a single awork time entry by its id, including its task, project, user, type of work and breaks.
- Search Clients
Returns up to 100 clients (companies) whose name contains the specified text.
- Search Projects
Returns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter.
- Search Users by Email
Returns the awork users whose contact information includes the specified email address.
- Update Client
Updates an existing client (company) by ID. Fields left blank keep their current values.
- Update Project
Updates fields (name, status, workflow, etc) on an existing awork project.
- Update Project Task
Updates fields (name, status, assignee, due date, etc) on an existing awork task.
- Update Time Entry
Updates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags.
- Find MPECs
Search Minor Planet Electronic Circulars by object or search terms, optionally filtered by issue date range.
- Find near-duplicate observations
Search the MPC's published observation database for near-duplicates of a given observation by time and angular proximity.
- Get action code
Resend an observation submission's action code (used to retract observations or label objects) to the email address on file.
- Get magnitude band
Retrieve reference information for a magnitude band used in MPC observations, or all bands.
- Get NEOCP observations
Retrieve observation data for an object currently on the Near-Earth Object Confirmation Page by tracklet identifier.
- Get object identifier
Look up the designations and identification details for a minor planet or comet given a name, provisional or permanent designation.
- Get observations
Retrieve recorded astrometric observation data for a solar system object by designation.
- Get observation status
Check the processing status of individual submitted observations by tracklet/station, observation ID, obs80 string, or submission block ID.
- Get observatory codes
Retrieve details for one or all observatories registered with the MPC by observatory code.
- Get orbital elements
Retrieve orbital elements and related parameters for a solar system object by designation.
- List objects
List solar system objects belonging to a named group such as NEOs, comets, or TNOs, ordered by designation.
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 awork
awork to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
awork to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
awork to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
awork to Google SheetsGoogle Sheets
awork to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
awork to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Minor Planet Center
Questions
awork and Minor Planet Center, answered
What can start an automation from awork?
Any of awork's 8 triggers in the catalog, including New Client, New Project, New Task and New Time Entry. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Minor Planet Center when something happens in awork?
Any of Minor Planet Center's 11 actions, including Find MPECs, Find near-duplicate observations, Get action code and Get magnitude band. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Minor Planet Center to awork?
Minor Planet Center has no triggers in the catalog today, so automations start in awork. If you need the other direction, ask: your agent reads Minor Planet Center's API documentation and adds it.
Do I have to build a connector for awork or Minor Planet Center?
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.