nexus_list_contactsLABSCO SUMMARY
One connection across the whole back office.
Ordering, stock, the customer's message thread and the social calendar sit behind the same key, so a question that arrives in a DM can end in a status change without moving between systems.
What it is
An operations platform for small and mid-sized retail reached over MCP: CRM contacts, the order lifecycle, inventory, omnichannel conversations across WhatsApp, Facebook Messenger and Instagram DMs, and Facebook and Instagram publishing with a content calendar.
What you get
- Contacts listed, read, created and updated, with one search across everything
- Orders created and read, listed, and moved through their status
- Stock checked and inventory listed before you promise a delivery
- Customer conversations listed and replied to across WhatsApp, Messenger and Instagram
- Social posts drafted, edited, scheduled, published, synced and deleted, with the content calendar and connected accounts beside them
- Per-post analytics for what has already gone out
Requirements
- An API key, which you trade for a token that lasts an hour; when it runs out, ask for a new one the same way.
- No Nexus organization yet? Start with the sign-up call (Step 0): it creates a free organization that can read and write but not send messages, and returns the key. Otherwise an admin in your organization creates the key (Step 1).
- No ready-made client settings are published, so you connect by sending the web requests yourself. The code is proprietary.
Setup effort
Follow the published steps — get an API key, trade it for a token, then call the server with that token
USE CASES
01
Answering "where is my order" in the thread it was asked in
Find the conversation, look up the order behind it, and reply on the same channel the customer used — WhatsApp, Messenger or Instagram.
02
Taking an order without opening the admin
Check the stock is really there, create the contact if they are new, and place the order in one pass.
03
Keeping fulfilment status honest
List what is open, then move each order to where it actually is — pending through to delivered — so the customer-facing status matches the warehouse.
04
Running the week's social calendar
See what is scheduled, draft the gaps, and publish or leave them queued — across the Facebook and Instagram accounts already connected.
05
Seeing what a post did
Pull the posts that have gone out and read their analytics, rather than opening each network's own dashboard.
06
Finding a customer you only half remember
One search runs across the platform; from the hit you can read the contact and correct whatever is out of date on it.
41 tools
Listed in project docs. Your client may show a different list.
nexus_get_contactnexus_create_contactnexus_update_contactnexus_list_ordersnexus_get_ordernexus_create_ordernexus_update_order_statusnexus_list_inventorynexus_check_stocknexus_list_conversationsnexus_send_messagenexus_searchnexus_sync_social_postsnexus_list_social_postsnexus_get_social_postnexus_create_social_postnexus_update_social_postnexus_publish_social_postnexus_delete_social_postnexus_list_social_accountsnexus_get_social_analyticsnexus_get_content_calendarnexus_list_organization_invitesnexus_invite_organization_membernexus_cancel_organization_invitenexus_resend_organization_invitenexus_list_internal_conversationsnexus_get_internal_messagesnexus_open_internal_dmnexus_send_internal_messagenexus_list_ai_tag_definitionsnexus_list_message_annotationsnexus_get_message_ai_annotationnexus_get_org_ai_annotation_settingsnexus_get_customer_conversation_intelligencenexus_get_conversation_intelligence_dashboardnexus_update_message_annotationnexus_update_ai_tag_definitionnexus_set_org_ai_annotation_promptnexus_update_org_conversation_intelligence_contextBEFORE YOU INSTALL
What to know first
Tools you get
41 tools named in the project's documentation.
INSTALLATION
Connect your client
Get an API key, trade it for a token, then call the server with that token.
Server setup
TERMINAL
# Step 0 (no Nexus organization yet): self-register a free agent-owned organization
curl -X POST "https://api.nexus.aiforstartups.io/functions/v1/agent-register" \
-H "Content-Type: application/json" \
-d '{
"agent_name": "my-agent",
"agent_platform": "cursor",
"owner_email": "<your-email>",
"organization_name": "<your-business-name>",
"plan": "free"
}'
# Returns: api_key (store it; it cannot be retrieved again), organization_id. Then go to Step 2.
# Step 1: A human admin creates an API key
curl -X POST "https://api.nexus.aiforstartups.io/functions/v1/agent-api-key-create" \
-H "Authorization: Bearer <human-admin-jwt>" \
-H "Content-Type: application/json" \
-d '{
"name": "my-agent",
"scopes": ["read", "write"],
"expires_at": "2026-12-31T23:59:59Z"
}'
# Returns: api_key (save this — shown only once), organization_id
# Step 2: Exchange API key for a short-lived JWT
curl -X POST "https://api.nexus.aiforstartups.io/functions/v1/agent-auth" \
-H "Content-Type: application/json" \
-d '{"api_key": "nxs_ak_..."}'
# Returns: access_token (JWT, 1 hour), organization_id
# Step 3: Use MCP
curl -X POST "https://api.nexus.aiforstartups.io/functions/v1/mcp-server" \
-H "Authorization: Bearer <jwt>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
