MCP Konektor.id in Claude

To connect Konektor.id to Claude, open Customize → Connectors in Claude, find Konektor, then select Connect. Sign in with your Konektor.id account and select the workspaces that Claude can use. You do not give Claude an API key.

The Konektor connector gives Claude access to the workspaces that you authorize: one, several, or all of them. Use the connector to inspect leads, the Inbox, WhatsApp rules, funnels, campaigns, tracking, and conversions without giving Claude an API key.

Baca panduan ini dalam bahasa Indonesia.

For other AI clients and a summary of the tool groups, read MCP Konektor.id.

What do you need to connect Konektor.id to Claude?

Confirm each prerequisite:

• Your workspace role is owner or admin.
• The workspace is in the 14-day trial, or uses a Starter, Pro, Enterprise, or Custom plan.
• The workspace subscription status is active or trialing.
• The selected workspace contains data that you can send to Claude.

The connector is not available to staff or viewers. It is also unavailable to Free plans and inactive subscriptions.

How do you connect Konektor.id to Claude?

These steps are the same in Claude on the web and in the desktop app.

1. Open Customize → Connectors in Claude, then select the Discover tab.
2. Type Konektor in the search field, then select the Konektor card.
   
3. Review the description and tool list, then select Connect.
   
   On a Claude Team or Enterprise account, the main button reads Connect for your team. Open the arrow beside it, then select Connect just for me if only you use this connection.
   
4. Sign in to Konektor if Claude asks you to authenticate.
5. On the consent screen, select the workspaces that Claude can use. Select All workspaces to also include workspaces where you become an owner or admin later. Review the permissions and the personal-data warning, then select Allow (Izinkan on the Indonesian screen).
   
6. Claude returns to the connector page and shows Connected.
   
7. Start a new conversation. Select + → Connectors, then make sure Konektor is on.
   

The connection is ready when Claude can run a Konektor tool and show results for the workspace you selected.

If you select more than one workspace, name the workspace in your request, for example "Use Konektor: show the newest leads in the Bandung Store workspace." Without a workspace name, Claude uses the first workspace that you selected.

Example requests

Write requests in plain language. Claude selects the matching Konektor tool. Before a tool runs for the first time, Claude asks for permission. Select Allow once for one call, or Always allow so Claude stops asking for that tool.

Pull lead data

Example request: "Use Konektor: show the 5 newest leads in my workspace with their status and source."

See what changed since yesterday

Example request: "What changed in my workspace since yesterday? What should I handle first?"

Claude shows new leads, leads that won or moved to a closing stage, chats past the reply target, failed conversions, and WhatsApp numbers that disconnected. Claude also flags unusual numbers, for example yesterday's leads far below the 7-day average.

Compare CS numbers

Example request: "Compare leads per CS number this month: how many came in and how many closed?"

Claude shows a table per WhatsApp number with masked numbers. You can also ask per team member or per city.

Save a segment

Example request: "Save a segment named Hot promo leads: leads from Meta Ads with the Promo tag from the last 30 days. How many leads does it have?"

Claude saves the filter. Then Claude shows the count and the 5 newest leads, each with a masked phone number. You can use the segment for a Meta audience.

Find a lead, a chat, or an order

Example request: "Find the lead, the chats, and the orders of Budi."

Claude shows up to 5 results of each type. Then Claude reads the one that you choose.

Audit the Inbox

Example request: "Audit my Inbox: how many chats are unreplied, how long do customers wait, and who has waited longest?"

Claude shows the unreplied count, the wait time, the reply speed, and the chats that need an answer. Customer numbers are always masked.

Create a WhatsApp rule

Example request: "Create a WhatsApp rule: when an incoming message contains 'sudah transfer', set the lead status to won. Keep the rule off for now."

Claude checks your existing rules, then shows the rule before it creates it. A new rule is always saved off. Turn it on from the dashboard, or ask Claude to turn it on after you agree with it.

Create or edit a Lead Form

Example request: "Create a consultation Lead Form with slug store-consultation in the Example Store workspace. Show the settings first."

Grant rotator read access to inspect settings and number options. Grant rotator write access to create or edit them. Existing connections do not gain rotator write permission automatically. Reconnect with a request for the required permission.

Claude can use a manual number or a WhatsApp session from an authorized workspace. Destination numbers and form settings can be sent to Claude. Session keys, QR codes, and provider credentials remain hidden. Creating a form does not send a WhatsApp message.

Name the rotator and requested changes when you edit it. Settings that you omit remain unchanged.

Manage webhooks

Example request: "List my webhooks. Which one failed in the last day?"

Claude shows each webhook with its last attempt, its last failure reason, and the number of failures in a row. Example request to create one: "Create a webhook to https://example.com/hooks for new leads and incoming Inbox messages. Send a test event after you create it."

Grant webhook read access to see webhooks. Grant webhook write access to create, edit, test, and delete them. Existing connections do not gain webhook write permission automatically. Reconnect with a request for the permission.

• Claude shows the address and the events, and asks for your agreement before it creates or changes a webhook.
• The signing secret appears one time only, in the answer after the webhook is created. Copy it at once. You can show it again in API & Webhooks.
• Only the workspace owner can use the webhook tools. The plan of the workspace must include webhooks.
• A test event goes to the address now. Claude shows the status that the address answered. It does not show the reply text.

Manage incoming webhooks

Example request: "Create an incoming webhook called Website form. Then wait for my test post and map the fields."

An incoming webhook is a secret address that other tools post leads to. Claude creates it, waits for your test post, reads the field paths of that post, and saves the mapping after you agree.

• The address appears one time only, in the answer after the webhook is created. Copy it at once and keep it private. Anyone who has it can add leads. You can show it again in API & Webhooks.
• Claude sees the field paths of your test post, the type of each value, and the length of a text. Claude never sees the values.
• Only the workspace owner can use these tools. The plan of the workspace must include the API.
• Grant webhook read access to list webhooks and read the field paths. Grant webhook write access to create, edit, and delete them.

Check tracking and conversions

Example request: "Check the latest conversion log to Meta and show the last 5 website tracking events."

More requests to try:

• "Show the funnel summary for this month."
• "Which campaign brought the most leads this week?"
• "Did any conversion fail to reach Meta in the last 7 days?"
• "Show all my WhatsApp rules that are on."

Research competitor ads

Example request: "Search the Meta Ad Library for competitor ads about 'english course'. Which ads have run the longest?"

Claude uses the Ads Research data of your workspace. More requests to try:

• "Show the competitors I watch and their new ads this week."
• "Which creative hook had the lowest cost per lead this month?"
• "Save this ad to the swipe file, then write a brief from my 3 best ads."

Each Meta Ad Library search uses the daily Ads Research quota. A creative brief uses AI credits, so Claude asks you first.

Ad write access in Claude

Default ad access is read-only. Existing connections never gain ad write access automatically.

Reconnect Claude with a request for ad write permission if you want to allow changes. The consent screen shows Ad write access only when the connection request includes it.

1. Review the requested workspaces and permissions.
2. Select I allow this app to change ads and budgets after my confirmation.
3. Select Allow.

Read-only connections do not need this permission. Select Cancel if you do not want the requested write access. Start the connection again with read-only permissions.

The AI Connections section in API & Webhooks shows an Ad write access badge for connections that have it. Revocation stops subsequent access.

Each campaign or budget change still needs your confirmation for that exact action. Always allow in Claude does not replace this confirmation. Activating a campaign can start spending budget.

Additional Meta tools in Claude require a ready Meta connection. Check Meta tools in Claude under Meta connection permissions in Ads Manager. Use Reconnect Meta if the permission is missing or has not been recorded.

If your workspace has more than one Meta ad account, Claude asks which account to use. Name the ad account you mean. Claude uses that account for the request.

Available tools

The connector provides tools under your connection permissions. Most lead, analytics, Inbox, and tracking tools are read-only. lead_update changes one lead when the connection has lead write permission. Ad tools require Ad write access for changes. rotator_create, rotator_update, inbox_send_message, inbox_conversation_update, inbox_label_create, quick_reply_create, quick_reply_update, whatsapp_template_create, whatsapp_templates_sync, the wa_flow_* tools, rule_create, rule_update, rule_set_active, rule_delete, conversion settings, tracking pixels, the webhook_* tools, the inbound_webhook_* tools, the agentic_* tools, business_profile_update, research_competitor_add, research_swipe_save, research_brief_create, meta_audience_create, meta_audience_lookalike_create, meta_audience_sync_now, conversion_resend, payment_link_create, leads_export_start, inbox_label_update, inbox_bulk_update, inbox_transcript_export, agentic_approval_decide, rotator_delete, whatsapp_qr_session_update, support_ticket_reply, onboarding_goal_set, segment_save, and segment_delete can also change data or make a file under their granted permissions. Delete tools require your confirmation.

The tools below are read-only, except for lead updates, authorized ad writes, rotator and rule changes, Inbox replies and changes, saved replies, conversion settings, tracking pixels, webhooks, incoming webhooks, Agentic settings, the business profile, Ads Research changes, Meta audience changes, conversion resends, payment links, lead exports, label edits and deletes, bulk chat changes, chat download links, agent approval decisions, Lead Form and form draft deletes, WhatsApp number edits, support ticket replies, the setup guide goal, and saved segments.

Aggregate tools do not send contact data. leads_list and lead_get can send personal data already stored in the workspace, such as a name, email address, or phone number. The Inbox tools send customer names and message text, with each customer number masked.

A reply goes to the customer only after you agree to the exact text. The permission Reply to and update Inbox conversations after you agree. Create and edit saved replies for your team. Edit and delete labels, change many conversations at once, and delete WhatsApp form drafts after you agree is off in a new connection. Reconnect and approve it if you want Claude to reply, update conversations, or manage saved replies and labels.

Retiring a form, creating a label, creating a template, and refreshing templates need an owner or an admin, as in the dashboard. Creating and changing saved replies, and saving the business profile, also need an owner or an admin. The change digest, reports per number, per team member, and per location, conversion health, order integration health, conversion resends, and payment links also need an owner or an admin. A connection made by another member gets a refusal. Only a connection made by the workspace owner can export leads. An API key cannot export leads. Label edits and deletes, Lead Form and form draft deletes, QR WhatsApp number edits, fresh official number health, AI agent activity and approvals, and the billing status also need an owner or an admin. Only the workspace owner can choose the setup guide goal.

Claude first shows the template with whatsapp_template_preview. That tool checks the WhatsApp rules and sends nothing. whatsapp_template_create sends the template to WhatsApp for review only after you agree to the full text. A pending template cannot be sent. A carousel, a video header, and a document header are made in the dashboard.

quick_reply_create and quick_reply_update save a reply only after you agree to the full text. A saved reply sends no message to a customer: the team chooses when to use it. A saved reply does not open a closed 24-hour reply window. Use a template for that.

conversion_resend sends one conversion again only after you agree. Claude can send again only a conversion that failed or was skipped. The ad platform gets the same event one more time, so check why it failed with conversion_logs first.

payment_link_create makes a payment link only after you agree to the lead, the amount, and the item name. The customer pays your Mayar store directly. Konektor does not send the link. After you agree, Claude can send it with inbox_send_message. A payment link needs a store key with Read & Write access. A Read Only key keeps working for orders, but it cannot make a link. A paid link comes in as an order of the lead, and payment_link_status reads its status. See Mayar integration.

leads_export_start makes a CSV file only after you agree to the filters. The file holds customer data: names, phone numbers, emails, and tracking data. leads_export_status gives a download link that works for 15 minutes. Anyone who has the link can download the file for 15 minutes, so do not share the link. The file stays available for 24 hours. Claude does not read the file.

inbox_bulk_update changes up to 50 chats at once. Claude first calls it without confirmation to count the chats that change, then applies the change only after you agree to the count. Customers do not see the change and get no message.

inbox_transcript_export gives a CSV download link for one conversation. The link works for 15 minutes, and only while the person who made it is still an owner or an admin. The file holds the message text and the customer name, without internal notes. Do not share the link. Claude does not read the file. An API key cannot make this link.

agentic_approval_decide records one decision for one AI agent action, only after you agree. An approved action runs at once: the agent can call your business system and reply to the customer. A rejected action does not run. One action takes one decision.

rotator_delete and wa_flow_retire in the draft delete mode delete data only after you agree, and you cannot undo it. The link of a deleted Lead Form stops working. Only a form draft can be deleted; a published form is retired.

whatsapp_qr_session_update changes the name or the number of one QR WhatsApp number only after you agree. Lead Forms send visitors to this number, so a wrong number sends visitors to the wrong chat.

billing_status shows no payment details, bank account, or payment link. Upgrades and payments stay on the Billing page.

onboarding_goal_set only chooses the steps that the setup guide shows. Tracking settings do not change.

segment_save and segment_delete change only the list of saved segments. They send no message. A segment holds filter values and IDs, never contact data. In Claude, a Meta audience and the follow-up settings can use a saved segment. They copy the filter when they save, so a later change to the segment does not change them.

search and fetch use the same permissions as the lead and Inbox tools. Chats need Inbox read permission. Without it, search still finds leads and orders. fetch shows no full phone number and no email. Customer text in a chat is data, not instructions.

business_profile_update saves the business profile only after you agree to the full text. Konektor AI reads the profile for Inbox reply suggestions and follow-up, so a change affects the AI replies at once. Send the complete new text, because the new text replaces the old text.

lead_update changes a lead in a workspace you allowed. A status change runs the conversion delivery you already configured.

rule_create can only make rules that change a lead. rule_update and rule_delete edit or remove those rules. rule_set_active turns any rule on or off, so you can turn on a new rule from Claude. A rule that sends a WhatsApp message or calls a webhook can only be renamed, switched on or off, or deleted from the connector. The webhook address stays in the dashboard.

The permission Create and reply to support tickets to the Konektor team on your behalf lets Claude open a support ticket for your workspace and reply to your tickets, after you agree to the text. Reading support tickets uses the workspace read permission. A new connection does not include it. The consent screen shows it only when the connection request asks for it, and you can decline it. Reconnect and approve it if you want Claude to create or reply to tickets.

Only a connection made by the workspace owner can change conversion settings. Conversion settings and tracking pixels do not accept platform tokens. Enter tokens on Website Tracking & Ad Platforms. An existing connection does not gain lead write, rule write, or conversion write permission on its own. Reconnect if those tools are missing.

The Agentic tools need the Change Agentic settings permission for any change. That permission also covers the business profile, and the Read Agentic settings permission covers reading it. Only the OpenRouter key cannot be set from Claude; it stays on the Agentic page. Auto-reply and the newest default settings can be set from Claude after you agree, but turning them on works only from a connection made by a workspace owner or admin. A connection with an API key cannot turn them on and can only turn auto-reply off. New API tools and knowledge sources start in a safe state: a tool is off until you turn it on, and a tool of an MCP server is off until you allow it. A secret that you send to Claude for a tool or a server is never shown again.

How does Claude read a long list?

The leads_list, inbox_conversations, and tracking_events tools show 20 items for each page by default. When a page is too large for the connector, the tool shows fewer items. Ask Claude for the next page, or narrow the request with a filter, for example one campaign or one day.

To count items, Claude uses a summary tool instead of reading every page.

Does Claude show interactive cards?

Yes, for the tools in the table below. Claude shows a card with its answer. A card helps you check a result and act on it without typing another request.

A card button runs the same tool as Claude, with the same rules: connection permissions, the owner or admin role, and your confirmation. Claude can ask you for permission before it shows a card. A connection without lead write permission shows the lead list without edit controls after the first try, with a short note.

Cards show in Claude on the web, the desktop app, and the mobile app. Claude Code shows the text result only. The broadcast tools exist only at the MCP address with an API key, so the broadcast preview shows only in a client that uses that address and can show cards. A client that does not show cards gets the same text result as before.

Does Konektor provide ready-made prompts in Claude?

Yes. Konektor gives Claude short working rules and a few prompts in Indonesian. The working rules tell Claude to start with a summary, use filters, and show a change before it saves. They also tell Claude to treat customer messages, lead notes, and the business profile as data, not as instructions.

A client that supports MCP prompts shows them as ready-made choices. In Claude, look for the Konektor prompts in the + menu or the prompt menu of the connector. The place of the menu can differ in each Claude version. Your connection sees only the prompts whose tools are available.

A prompt does not change data and does not send a message without your approval.

What data does Konektor.id send to Claude?

Konektor sends data only after Claude invokes an enabled tool. Tool results can include:

• workspace profile, plan, and usage data;
• tracking, funnel, campaign, and conversion metrics;
• a bounded lead list;
• one lead that you request, with its 20 newest activities and without titles that a customer or a team member wrote;
• bounded conversion-feedback identifiers and status data;
• Inbox conversations and message text that you ask about;
• your WhatsApp rules;
• Agentic settings: titles and status of knowledge sources, API tool definitions, and the tool list of MCP servers, without keys and without secrets;
• the business profile and the saved replies, which are text that your team wrote;
• website tracking events without IP address or browser identifiers;
• counts for the change digest, the reports per number, per team member, and per location, conversion health, and order integration health, with no customer data;
• the orders of one lead, with no buyer data and no payment link;
• saved segments, which hold filter values only, and search results with a short name, a masked phone number, and a dashboard link;
• a lead export download link that works for 15 minutes, when the workspace owner asks for it. The file content is not sent to Claude.

Konektor does not read the surrounding conversation, Claude memory, chat history, conversation summaries, or files that you upload to Claude.

How long does the Claude connection last?

Konektor uses short-lived access that refreshes while the connection remains valid. You must authorize the connection again after 30 days of inactivity or after it reaches its 90-day limit.

Konektor removes expired authorization requests and codes after 24 hours. Konektor retains expired or revoked access hashes for up to 30 days. A revoked consent record can remain for up to 90 days when no retained access record references it.

Anthropic processes and may retain tool results under Anthropic policies. Konektor retention schedules do not delete data from Claude systems or conversation history. Read the Konektor Privacy Policy and the Anthropic Privacy Center before connecting personal data.

How do you revoke Claude access to Konektor.id?

You can disconnect access from Claude or Konektor.

Disconnect from Claude

1. Open Customize → Connectors.
2. Find Konektor.
3. Select Disconnect.

Revoke from Konektor

1. Open Settings > API & Webhooks for the workspace. For a connection to several workspaces, open the first workspace that you selected.
2. Find AI Connections, then select the Claude connection.
3. Select Revoke access for the connection.
4. Confirm the action.

Konektor rejects the next call after you revoke the grant. Disconnecting does not automatically remove tool results already stored in Claude conversation history.

Troubleshoot the connection

Contact support@konektor.id for product help. Report security issues to security@konektor.id.

Use the advanced MCP endpoint

The directory connector uses this OAuth endpoint:

https://mcp.konektor.id/mcp/claude

The https://mcp.konektor.id/mcp endpoint remains available for advanced API-key integrations. The advanced endpoint has a separate catalog and scopes, including write capabilities when the plan and key permit them.

Read Agent API v2 and advanced MCP for API-key configuration. Do not use the advanced endpoint when the Claude connector meets your requirements.

The WhatsApp broadcast tools (broadcasts_list, broadcast_preview, broadcast_create, broadcast_schedule, broadcast_pause, broadcast_resume, broadcast_cancel, broadcast_report, and whatsapp_optout_set) exist only at the MCP address that uses an API key, https://mcp.konektor.id/mcp. The Konektor connector in Claude does not offer them. Read WhatsApp Broadcast in the Agent API.

Do I need to give Claude an API key?

No. Claude signs in with your Konektor.id account and your approval on the consent screen. You choose the workspaces that Claude can use, and you see the requested permissions before you select Allow.

Can Claude change data or reply to customers without my approval?

Claude uses only the permissions that you approve on the consent screen. A reply goes to the customer only after you agree to the exact text. Claude saves the business profile and a saved reply only after you agree to the full text. A new WhatsApp rule is always saved off. Each campaign or budget change still needs your approval for that exact action.

Does Claude see customer phone numbers?

In the Inbox, customer numbers are always masked. The lead tools can send personal data already stored on the lead that you ask for, such as a name, email address, or phone number. Aggregate tools do not send contact data.

Which workspace does Claude use if I select more than one?

Name the workspace in your request. Without a workspace name, Claude uses the first workspace that you selected on the consent screen.

How do I limit the tools that Claude sees?

Add toolsets and read_only=true to the connector address. Claude then sees fewer tools. It reads fewer tool descriptions, uses fewer tokens, and picks the correct tool more often.

The Konektor connector that you add from the Claude directory uses a fixed address with all tool groups. To pick groups, add Konektor as a custom connector. Use an address like this:

https://mcp.konektor.id/mcp/claude?toolsets=leads,inbox&read_only=true

1. In Claude, open Customize > Connectors, then select Add custom connector. On a Team or Enterprise plan, an Owner adds the custom connector in Organization settings > Connectors.
2. Enter a name and paste the address with the groups that you want.
3. Add the connector. Then sign in with your Konektor.id account and select the workspaces, the same as in the steps above.

toolsets=leads,inbox shows only the lead and Inbox tools. read_only=true shows only the tools that read data. Remove a parameter that you do not need.

To change the groups later, edit the address of the connector in Customize > Connectors. The permissions that you approve on the consent screen still apply first.

The group names and what each group covers are in Choose tool groups and read-only mode.

Why is a tool missing in Claude?

Enable the connector for the conversation and review tool permissions in Claude. An existing connection does not gain new permissions on its own, for example lead write or Inbox reply. Select Connect again and approve the new permissions if the tool is still missing. A connection address with toolsets or read_only=true hides the other tools, so change the groups if you need them.