Leadoku
Leadoku is a platform designed to streamline lead management and sales processes.
Verdict
Common use cases
- Draft personalized LinkedIn follow-ups for new connections
- Identify high-priority leads from recent outreach
- Generate weekly connection summaries for sales standup
- Spot patterns in connection acceptance rates
- Prepare context for SDR handoff calls
Integration
- Vendor
- Leadoku
- Category
- crm
- Auth
- API_KEY
- Tools
- 1
- Composio slug
leadoku
Tools
- Get New Connections
Retrieves a list of new connections from growth-x (formerly leadoku). the 'tsfield' for this action is 'connection date' (mapped from 'creation date' in the api response).
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Leadoku in the CRM category and click Connect. 3. You'll be prompted to enter your Growth-X API key — retrieve this from your Growth-X account settings under API Access. 4. Paste the key into Switchy and click Authorize. 5. Switchy will confirm the connection is active. 6. Open any Space and type '@Leadoku get my new connections from the last 7 days' to test. 7. The MCP will return a list with names, LinkedIn URLs, and connection dates. 8. If you see results, the integration is working — you can now ask Leadoku to filter by date range or export connection data for follow-up workflows.
What teammates see: by default, memories from Leadoku 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
Starter prompts
Recent Connection Summary
@Leadoku get all new connections from the past 7 days, then summarize them in a bulleted list with name, title, and company.Open in a Space →
Prioritize Follow-Ups
@Leadoku fetch new connections from the last 14 days, then flag anyone with 'Director' or 'VP' in their title at companies with 50-500 employees.Open in a Space →
Draft Personalized Messages
@Leadoku get connections from the past 3 days, then write a short, friendly follow-up message for each person mentioning their role and how our product helps their team.Open in a Space →
Weekly Outreach Report
@Leadoku pull all new connections from the past week and create a table with columns for name, company, title, and connection date.Open in a Space →
Spot Industry Trends
@Leadoku get new connections from the last 30 days, then group them by industry and show me which sectors are most represented.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Leadoku show me all new connections from the last 7 days
Here are your recent connections from Growth-X: • Sarah Chen (Product Manager at Stripe) — connected 2 days ago • Marcus Williams (VP Sales at Notion) — connected 4 days ago • Priya Sharma (Founder at Cascade AI) — connected 6 days ago • 12 additional connections retrieved All connections include LinkedIn profile links and connection timestamps. This data reflects your Growth-X account state as of the query time.
This example shows the MCP's core read capability: fetching timestamped connection records. Requires a valid Growth-X API key with read access to connection data. The MCP maps 'creation date' from the API to 'connection date' in responses — useful for time-based filtering but won't capture custom fields you've added in Growth-X.
@Leadoku find connections made this month and group them by company domain
Connections by company (last 30 days): **stripe.com** — 3 connections (Sarah Chen, David Park, Lisa Tran) **notion.so** — 2 connections (Marcus Williams, Alex Rivera) **Individual contributors** — 8 connections across various companies Total: 13 new connections this month. Note that company grouping is inferred from LinkedIn profile data returned by Growth-X; accuracy depends on profile completeness.
This synthesis example pairs the MCP's connection retrieval with AI reasoning to group and summarize. The MCP itself only fetches raw connection lists — the grouping logic happens in the AI layer. Useful for spotting outreach patterns, but won't reflect any custom tagging or segmentation you've done inside Growth-X's own interface.
@Leadoku pull connections from the last 48 hours and draft a follow-up message template for product managers
Found 4 connections in the last 48 hours. 2 are product managers: • Sarah Chen (Stripe) • Olivia Martinez (Figma) **Draft follow-up:** 'Hi [Name], great connecting on LinkedIn! I noticed you're working on [their company]'s product side — I'd love to hear how your team thinks about [relevant pain point]. Are you open to a quick 15-min chat next week?' This template assumes B2B SaaS context; adjust tone and specificity based on your actual outreach goals.
This example shows how the MCP's connection data feeds downstream AI tasks like drafting outreach. The MCP retrieves names and roles; the AI generates the message. No write-back to Growth-X happens here — you'll need to copy the draft into your outreach tool manually. Rate limits on the Growth-X API may throttle frequent queries if you're polling hourly.
Use-case deep-dives
When Leadoku makes sense for small outbound teams
A 3-person sales team running LinkedIn outreach through Growth-X needs to triage new connections every morning before calls start. The Leadoku MCP pulls yesterday's connections into Switchy so the team can batch-assign follow-up tasks without opening the Growth-X dashboard. This works when your connection volume is under 50 per day and you're already using Growth-X for automation. If you're running multiple outreach tools or need to cross-reference CRM data, the single-tool scope here gets limiting fast. The buying call: if Growth-X is your only outbound engine and you want connection data in your AI workspace without tab-switching, this MCP delivers that one thing cleanly.
Leadoku for founder-led sales check-ins
A solo founder or two-person founding team doing their own outbound can use the Leadoku MCP to review new LinkedIn connections during a Friday pipeline sync. The MCP surfaces who connected this week so the founder can decide which leads to prioritize without logging into Growth-X. This scenario breaks down if you need enrichment data, email sequences, or CRM sync—Leadoku only returns connection dates and names. If your outbound motion is purely LinkedIn-first and you're under 20 connections per week, this keeps the review lightweight. The threshold: once you're managing multiple channels or need to route leads to a CRM automatically, you'll outgrow this MCP's single-action scope within a quarter.
When Leadoku fits agency LinkedIn audits
A 5-person growth agency managing LinkedIn campaigns for 8 clients can use the Leadoku MCP to pull connection data into Switchy for monthly client reports. The MCP retrieves new connections by date so the agency can compare growth across accounts without exporting CSVs from each Growth-X workspace. This works when clients are all on Growth-X and the agency only needs connection counts and timestamps, not engagement metrics or message response rates. If clients expect deeper analytics or multi-platform reporting, the MCP's single-tool limitation means you'll still need a BI tool or manual aggregation. The call: for agencies doing lightweight LinkedIn audits with Growth-X-only clients, this MCP saves 15 minutes per account per month.
Frequently asked
What does the Leadoku MCP do in Switchy?
It pulls your new LinkedIn connections from Growth-X (formerly Leadoku) into Switchy, so your AI agents can see who connected recently and when. The MCP maps Growth-X's 'creation date' field to 'connection date' for easier querying. You can then route these leads into workflows, enrich them with other MCPs, or log them to your CRM without manual exports.
Do I need admin access to connect Leadoku?
No admin role required — you just need an API key from your Growth-X account. Generate it in Growth-X's settings, paste it into Switchy's auth form, and the MCP will start fetching connections immediately. Anyone on your team with API-key access can connect it; Growth-X doesn't enforce role-based key permissions.
Can the Leadoku MCP send messages or accept connection requests?
No. It only reads your new connections list — it can't send LinkedIn messages, accept requests, or write data back to Growth-X. If you need outbound automation, use Growth-X's native campaigns or pair this MCP with a messaging tool like Slack to notify your team when high-value connections appear.
How is this different from exporting connections from Growth-X manually?
Manual exports are static CSVs you download once. The Leadoku MCP gives your AI agents live, queryable access to connection data inside Switchy — no downloading, no re-uploading. You can trigger workflows the moment a new connection appears, filter by date ranges on the fly, and combine connection data with other MCPs in a single prompt.
Who on the team should connect the Leadoku MCP?
Whoever owns your Growth-X account and has the API key. Typically that's your sales ops lead or the person running LinkedIn outreach campaigns. Once connected, any Switchy user in your workspace can query the connection data — the MCP doesn't create per-user seats or count against Growth-X's user limits.