MCP integration
Connect ComingUp to another MCP client
Use a compatible remote MCP client with ComingUp’s normal sign-in and authorization flow.
Why connect ComingUp
A compatible assistant may use the same approved ComingUp capabilities without requiring an API token or a different household workflow.
After connecting
Ask for what you want in normal language; there are no MCP commands or special syntax to learn. When a request clearly relates to ComingUp, compatible assistants can usually select the connection themselves. Automatic connection selection is controlled by the AI provider and can vary by client, plan, and conversation. If the assistant does not select ComingUp, say “use ComingUp” as a simple fallback.
Integration details
Other MCP clients
ComingUp provides a standards-compatible remote MCP endpoint for clients that support compatible remote MCP connections and authorization.
Current compatibility
Support varies by MCP client. ComingUp cannot guarantee compatibility with every protocol version, transport, authorization implementation, plan, or application.
Depends on the client
Every client manages its own directory or catalog. Check the client’s current documentation rather than assuming ComingUp is listed.
Manual remote MCP connection
Use these steps where the client supports a remote MCP server with a browser-based authorization flow.
Integration details
ComingUp MCP
Connect compatible AI assistants to approved ComingUp household capabilities.
Supported capabilities
Account and connection
Understand the connected ComingUp account, the active household and general connection state, and the permissions currently approved.
Schedule and events
Check schedules, find event details, create or update ComingUp events, create supported recurring events, update a series, or change one occurrence.
Lists
See household lists, create a list, and add, change, check, uncheck, or remove list items, including clearing completed items where supported.
Notes
Find and read household notes, create new notes, and update existing notes.
Contacts
Find household contacts and save useful new contacts.
Recipes
Find and read recipes, save private household recipes, and update private recipes.
Household context
Use safe context such as household name, timezone, and people to make requests more useful.
Deliberate limits
- No permanent deletion. ComingUp does not expose permanent deletion of durable top-level household data through this connection.
- Excluded areas. Photos and media, billing changes, and household administration are not exposed.
Official resources
Setup steps
Find the remote MCP connection area
Find the client’s custom MCP or remote MCP connection area.
Add the endpoint
Add the code-owned remote MCP endpoint.
https://api.comingup.today/mcpAuthorize ComingUp
Follow the ComingUp sign-in and authorization flow.
Review permissions
Review the requested permissions.
Ask naturally
Ask the assistant naturally. If necessary, explicitly say “use ComingUp.”
Reconnect ComingUp
If ComingUp access expires or stops working, reconnect ComingUp from the client’s connection settings. The client should send you through ComingUp’s normal authorization flow again. Review the requested permissions before approving. Write access is available only for the permissions you approve.
Disconnect or revoke access
To disconnect ComingUp, use the client’s supported disconnect, remove-connection, or remove-server control. After access is revoked, that client can no longer use that authorization. Reconnecting requires the normal ComingUp authorization flow again. Connected external calendar events remain externally owned and read-only. If reconnecting or disconnecting fails, consult the client’s connection documentation or contact support@comingup.today.
Connection address
Remote MCP endpoint
Copy this exact address into a compatible remote MCP client.
https://api.comingup.today/mcpWhat can I ask?
“What do we have going on this weekend?”
“Save this recipe to ComingUp.”
“What ComingUp permissions do you have?”
Troubleshooting basics
- Confirm that the client supports remote—not only local—MCP servers.
- Confirm that the client supports browser-based authorization for a remote MCP connection.
- Never work around an authorization problem by pasting a password, access token, refresh token, API key, or secret into the client.