chore: sync agent connector docs from production API

[Pranesh-Raghu]

Summary

• Ran node scripts/sync-agent-connectors.js against production API to regenerate all connector documentation
• Synced 165 connectors, 4980 tools
• 57 files updated: MDX connector pages, TypeScript data files, catalog.ts

Changes

• src/content/docs/agentkit/connectors/ — regenerated MDX pages for all connectors
• src/data/agent-connectors/ — updated tool data TS files
• src/data/agent-connectors/catalog.ts — updated connector catalog

No manual content changes — all changes are from the production API sync.

Summary by CodeRabbit

• New Features

  • Added many new agent connectors and tool registries (ConvertAPI, Databox, Deepgram, DevRev, DocsAutomator, Echtpost, Eraser, Fibery, FullEnrich, Hugging Face, Kit, Lemlist, Mem0, Memberstack, Motion, Pendo, Prisma, Twilio) and expanded the connector catalog.

• Documentation

  • Added Quickstarts, credential/OAuth setup, capability lists, and tool catalogs for each connector; added connector setup guides/templates.

• Improvements

  • Updated Figma, Outlook, and HubSpot connector capability listings and tool parameter schemas.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e41d12f8-ecaf-4508-a839-97e0db7cc876

📥 Commits

Reviewing files that changed from the base of the PR and between aef58a5 and f34ae25.

⛔ Files ignored due to path filters (1)

• src/assets/docs/agent-connectors/devrevmcp/personal-access-token.png is excluded by !**/*.png

📒 Files selected for processing (1)

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📜 Recent review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Redirect rules - scalekit-starlight
• GitHub Check: Header rules - scalekit-starlight
• GitHub Check: Pages changed - scalekit-starlight

🧰 Additional context used

📓 Path-based instructions (8)

**/*.mdx

📄 CodeRabbit inference engine (.cursorrules)

**/*.mdx: Use clear, descriptive titles that explain the purpose of the document
Include comprehensive descriptions in frontmatter metadata
Organize content with logical heading hierarchy (H2, H3, H4)
Use tableOfContents property in frontmatter when content has multiple sections
Set appropriate sidebar labels for navigation in frontmatter
Use direct instruction writing style with phrases like 'This guide shows you how to...' and 'Create an authorization URL to...'
Use second person perspective ('your application', 'you receive', 'you must') in documentation
Keep sentences concise, aiming for under 25 words per sentence
Explain the 'why' in documentation with phrases like 'This prevents CSRF attacks by...' or 'Use this to validate that...'
Use action verbs in section headings: 'Store session tokens securely', 'Validate the state parameter', 'Exchange authorization code for tokens'
Use present tense for descriptions: 'Scalekit handles the complex authentication flow', 'The SDK provides methods to refresh tokens'
Use future tense for results: 'This will redirect users to...', 'You'll receive a JWT containing...', 'Scalekit returns an authorization code'
Use transition phrases between sections: 'After the user authenticates...', 'Once the state is validated...', 'Let's take a look at how to...'
Write 1-3 opening paragraphs that explain what users will accomplish, provide context about when/why, preview key concepts, and use direct instructional language
Begin introduction sections with a clear statement of what the guide covers and explain the problem being solved
Use collapsible sections in introduction for sequence diagrams, video demonstrations, data models, and JSON examples with appropriate icons
Use numbered format within Steps component: 1. ## Title with all step content indented with exactly 3 spaces
Use action-oriented headings in step-by-step guides within Steps components
Include code examples in all 4 languages (Node.js, Python, Go, Java) within Steps co...

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

---

⚙️ CodeRabbit configuration file

**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:

Frontmatter

• title MUST be ≤ 60 characters and clearly state what the page does.
• description MUST be ≤ 160 characters, action-oriented, unique per page.
• sidebar.label MUST be present and ≤ 30 characters.
• sidebar.order MUST be set on every page that lives inside a section
  with siblings, to enforce the journey order in sidebar.config.ts.
• Flag any missing prev / next links on pages that are clearly
  part of a sequential flow (e.g., quickstart → implement-login →
  complete-login → manage-session → logout).

Voice & Style (CLAUDE.md standards)

• Voice: confident, direct, collaborative, instructional.
• Person: second person only ("you", "your application"). Reject "we",
  "our", "the developer", "the user".
• Tense: present tense for descriptions; imperative mood for instructions.
• Flag weasel words: "simply", "just", "easy", "straightforward",
  "obviously", "of course", "note that".
• Flag passive voice constructions where active voice is clearer.
• Headings must be sentence case, not Title Case (except proper nouns).
• Headings that match a real API parameter, method, or field name
  (e.g., contactID, xero_tenant_id, executeTool) should preserve
  the original casing. Do NOT flag these as sentence-case violations.
• No heading should end with a colon or period.

Content structure

• Journey how-to guides MUST contain numbered <Steps> (Starlight
  component). This does NOT apply to src/content/docs/cookbooks/**
  (blog-style recipes — optional <Steps>, <Tabs> after </Steps> OK;
  see cookbooks path_instructions).
• Concept pages MUST NOT contain numbered steps — concepts explain, not instruct.
• API reference pages MUST list parameters in a table with Name / Type /
  Required / Description columns.
• Every page MUST end with a clear "what's next" signal — either a
  next: f...

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**/*.{yml,yaml,md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/browsecentral-labels.mdc)

**/*.{yml,yaml,md,mdx}: BrowseCentral labels should be maximum 3-5 words - keep concise but add context when needed
BrowseCentral labels should be action-oriented - start with verbs when possible
BrowseCentral labels should be specific and clear - add context when simple labels are ambiguous
BrowseCentral labels should be outcome-focused - describe what users accomplish and the context
BrowseCentral labels should use 'Action + Object' pattern (e.g., 'Invite users', 'Restrict sign-up', 'Set up SCIM')
BrowseCentral labels should use feature names (e.g., 'Enterprise SSO', 'Passwordless quickstart')
BrowseCentral labels should describe task completion (e.g., 'Run migrations', 'Migrate auth', 'Merge identities')
BrowseCentral labels should include specific context when needed (e.g., 'Configure Scalekit MCP server', 'Validate incoming API requests')
BrowseCentral labels should use integration context when applicable (e.g., 'Build MCP auth with your existing auth system')
BrowseCentral labels should avoid instructional prefixes: 'How to', 'Guide to', 'Implement', 'Configure', 'Learn', 'Understand'
BrowseCentral labels should avoid verbose phrases: 'Step-by-step guide', 'Complete tutorial', 'Detailed documentation'
BrowseCentral labels should avoid weak verbs: 'Enable', 'Allow', 'Provide', 'Support'

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/deno-docs-style.mdc)

**/*.{md,mdx}: Use sentence case for all titles and headings in MD/MDX documentation
Keep page titles short and descriptive (3–7 words when possible) in MD/MDX documentation
Use outcome-focused headings that describe results, not categories (e.g., 'Run a script' not 'Scripts')
Avoid gerunds in headings when an imperative works - prefer 'Configure proxies' over 'Configuring proxies'
Keep sidebar labels concise (1–3 words), use sentence case, and focus on outcomes or objects
Use sentence case in sidebar labels without punctuation
Set frontmatter title in sentence case with a clear outcome; description in one sentence (≤160 chars); sidebar.label as shorter form of title; enable tableOfContents on longer pages
Start documentation pages with a one-paragraph overview explaining what the page covers and when to use it
Present the primary use case (80% path) first in documentation, with edge cases later
Use numbered steps for task-focused sections in documentation, with each step beginning with a verb
Break up long documentation sections with subheadings every 3–6 paragraphs
Use asides for important notes, tips, cautions, and references in documentation
Provide runnable, minimal code examples that work as-is in documentation
Prefer CLI-first examples and show file layout when helpful in documentation
Label code blocks with titles for context (e.g., 'Terminal', 'main.ts') in documentation
Keep code block annotations brief and purposeful - annotate only what matters
Use consistent variable and file names across a documentation page
Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')
Prefer relative links for internal documentation pages and include anchors for section references
Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints
Use backticks for code, file names, CLI flags, and endpoints in documentation
Use lists for options and features in documentation; tables only when comparisons are cleare...

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**/*.{ts,tsx,py,go,java,mdx,md}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{ts,tsx,py,go,java,mdx,md}: Use the exact SDK variable names: Node.js (scalekit), Python (scalekit_client), Go (scalekitClient), Java (scalekitClient)
Never hard-code secrets or API keys in code examples; use environment variables
Include security comments that state the threat, why the pattern is required, and what can go wrong if omitted

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**/*.{mdx,md}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{mdx,md}: All code examples must use <Tabs syncKey="tech-stack"> format and include Node.js, Python, Go, and Java implementations (90% rule)
Use sentence case for all titles and headings in documentation
Use bold for first mention of important terms, UI elements, and dashboard paths (e.g., Dashboard > Authentication > Session Policy)
Use inline code for technical identifiers: variables, functions, endpoints, scopes, environment variables, file paths, and placeholders
Always include headers in tables; keep cell content concise and readable
Prefer fenced code blocks with language identifiers for all code; never use screenshots of code
Use descriptive link text; never use 'click here' or 'this' as link labels
Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns
Use active voice; prefer 'Run the command' over 'The command should be run'
Use second person when giving instructions; address the reader as 'you'
Use present tense for procedures; 'This command installs…' not 'This command will install…'
Avoid hype, slang, and filler words like 'simply', 'just', 'obviously' in documentation
Use consistent terminology throughout; prefer standard names over synonyms
Explain security implications and threats for all security-related content
Use imperative verbs for procedure headings: 'Run a script' not 'Running a script'; 'Configure proxies' not 'Configuring proxies'
Headings must describe outcomes, not categories (good: 'Run a script'; bad: 'Scripts')
Split content into clear sections with descriptive, sentence-style titles that convey meaning without requiring the following paragraph
Keep paragraphs short; isolate critical points in their own short paragraphs
Begin sections and paragraphs with standalone topic sentences that preview content
Put the topic words at the beginning of topic sentences to support fast skimming
Put key takeaways and results at the top of documents and sections
Use bullets and tabl...

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**/*.{md,mdx,astro,ts}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.{md,mdx,astro,ts}: Use pnpm pretty-quick --staged via pre-commit git hook to auto-format all staged .md, .mdx, .astro, .ts files with Prettier
Run pnpm format to auto-format all .md, .mdx, .astro, .ts files before pushing changes

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

src/components/templates/agent-connectors/_setup-*.mdx

⚙️ CodeRabbit configuration file

src/components/templates/agent-connectors/_setup-*.mdx: These are connector setup templates. Override the global MDX rule:

• Do NOT require all four SDK language tabs. Setup templates show
  auth-redirect and credential configuration which may only apply
  to Node.js and Python. Require tabs ONLY when the snippet
  demonstrates Scalekit client SDK usage (scalekit / scalekit_client).
• DO check: missing os or other standard library imports in
  Python snippets, and missing require/import in Node.js snippets.

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

**

⚙️ CodeRabbit configuration file

**: # CLAUDE.md - Scalekit Documentation Guide

Overview

This file is the single source of truth for all documentation standards and AI assistant guidelines in this repository. All documentation must adhere to the rules defined below.

---

Core Principles

Documentation-first development

Every feature must include comprehensive, user-focused documentation. Documentation is not an afterthought but a first-class deliverable that guides implementation. All code changes require corresponding documentation updates.

Git workflow

• Do NOT include Co-Authored-By lines in commit messages
• At the start of a fresh session, before making any changes, ask the user: "Do you want me to cut a new branch or work on the current branch?"
• Never force push (git push --force or git push -f). If a push fails, stop and clearly explain the reason it failed — do not attempt workarounds without user confirmation.
• For commit, push, and PR creation, spawn a subagent using the Haiku model to handle it. The pre-push hook generates large logs and PR creation output adds unnecessary noise to the main session context.
• Once the user confirms local testing works, or explicitly asks to commit and push, commit all changes, push the branch, and open a PR against main. The PR must include:
  • A crisp description of the changes
  • A preview link in the format: https://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/{path-to-changed-page}/

SDK variable names (critical)

CRITICAL: Use the exact variable names below in all documentation and code examples.

• Node.js: scalekit
• Python: scalekit_client
• Go: scalekitClient
• Java: scalekitClient

Multi-Language SDK Consistency

All code examples MUST include Node.js, Python, Go, and Java implementations with consistent variable naming conventions. Examples must show both success and error handling paths. Security implications must be explained for each implementation....

Files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

🧠 Learnings (17)

📚 Learning: 2026-02-25T03:34:41.147Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:31-31
Timestamp: 2026-02-25T03:34:41.147Z
Learning: In MDX files, import { Code } from 'astrojs/starlight/components' only if the MDX content actually uses the <Code> component. If the file uses only fenced code blocks (```), the import is not required. Apply this guideline to all MDX files (e.g., src/content/docs/**/*.mdx) to avoid unnecessary imports and reduce bundle size.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-02-25T18:41:00.639Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 446
File: src/content/docs/authenticate/m2m/api-auth-quickstart.mdx:78-78
Timestamp: 2026-02-25T18:41:00.639Z
Learning: Preserve full URLs inside code comments in MDX code blocks (bash/python/js) when the URLs are part of copyable examples. Do not flag these in code examples. Use relative paths in prose and hyperlinks within MDX; only enforce relative paths for markdown prose links, not for URLs inside code comments.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-16T17:25:30.736Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 693
File: src/content/docs/authenticate/mcp/troubleshooting.mdx:170-170
Timestamp: 2026-05-16T17:25:30.736Z
Learning: In this repo’s documentation (.mdx files), external links should be written using plain Markdown link syntax: `[text](url)`. Do not flag links for missing `target="_blank"` or `rel="noopener"` (avoid adding raw HTML anchors just to include those attributes), and keep the approach consistent with existing docs styling.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-10T10:37:47.033Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-asana.mdx:15-15
Timestamp: 2026-03-10T10:37:47.033Z
Learning: In src/components/templates/agent-connectors/**/*.mdx, it is acceptable to reuse a single shared redirect URI screenshot (use-own-credentials-redirect-uri.png) across multiple steps within the same connector file, even if different UIs are shown. Do not flag this reuse as an issue; ensure this behavior is intentional and documented for reviewers.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-10T10:38:27.783Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-confluence.mdx:16-16
Timestamp: 2026-03-10T10:38:27.783Z
Learning: In all MDX templates under src/components/templates/agent-connectors, the pattern uses empty alt text (e.g., ![]()) for redirect URI screenshots like use-own-credentials-redirect-uri.png. This is intentional; reviews should not flag missing alt text for these images in this directory.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-12T16:26:39.422Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-bigquery.mdx:18-22
Timestamp: 2026-03-12T16:26:39.422Z
Learning: In agent-connectors MDX templates, it is acceptable to reuse shared Google OAuth screenshots stored under `@/assets/docs/agent-connectors/gmail/` (e.g., oauth-web-app.png, add-redirect-uri.png) across different Google-service connector templates (e.g., _setup-bigquery.mdx, _setup-google-ads.mdx). Do not flag cross-connector image path reuse within Google service connectors as an issue. This guideline applies to all files in this directory.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-10T10:38:30.012Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-clickup.mdx:17-17
Timestamp: 2026-03-10T10:38:30.012Z
Learning: In the repository's agent-connectors setup template files (src/components/templates/agent-connectors/_setup-*.mdx), the pattern for redirect URI screenshot images is to use empty alt text (![]()). Do not flag missing alt text for these specific Markdown image syntaxes in the agent connector setup template files. This guidance applies only to files matching this setup-*.mdx naming pattern; other templates should continue to enforce standard alt text practices.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-12T16:28:37.168Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:37.168Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, external links should not be flagged for missing target="_blank" and rel="noopener". Plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) is acceptable and intentional in these agent-connector setup templates, following the established pattern across all connector templates in this directory.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-03-12T16:29:08.626Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-onenote.mdx:12-12
Timestamp: 2026-03-12T16:29:08.626Z
Learning: In files matching src/components/templates/agent-connectors/_setup-*.mdx, permit and reflect the branding 'Azure Active Directory' (AAD) as intentional. Do not flag or update these agent-connectors setup templates for references to 'Microsoft Entra ID'. This exception applies only to these setup template files; maintain standard branding elsewhere according to project guidelines.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-21T11:45:36.989Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 712
File: src/components/templates/agent-connectors/_setup-fellowaimcp.mdx:16-16
Timestamp: 2026-05-21T11:45:36.989Z
Learning: For MDX documentation files matching src/components/templates/agent-connectors/_setup-*.mdx, do not flag third-person phrasing (e.g., “The user is redirected…”, “The user must have…”) as a violation of any second-person-only writing guideline. This agent-connector setup template pattern is explicitly exempt; the second-person-only rule continues to apply to other MDX documentation pages.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-21T11:45:34.201Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 712
File: src/components/templates/agent-connectors/_setup-supermetricsmcp.mdx:16-16
Timestamp: 2026-05-21T11:45:34.201Z
Learning: For agent-connector setup template MDX files matching src/components/templates/agent-connectors/_setup-*.mdx, allow intentional third-person phrasing (e.g., “The user is redirected…”, “The user must have…”). Do not treat “The user” as a voice/person violation in these specific template files, and do not apply the second-person-only rule to them.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-06-02T10:23:08.719Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 731
File: src/components/templates/agent-connectors/_setup-googlelooker.mdx:72-79
Timestamp: 2026-06-02T10:23:08.719Z
Learning: In production-synced agent connector setup templates (e.g., `src/components/templates/agent-connectors/_setup-*.mdx`), TypeScript SDK snippets that appear as single-language blocks (such as `scalekit.actions.getAuthorizationLink`) are intentional. Do not flag these snippets for missing language tabs/options, even when the content specifically demonstrates Scalekit client SDK usage.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-04-25T07:22:18.321Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 633
File: src/components/templates/agent-connectors/_setup-heyreach.mdx:12-12
Timestamp: 2026-04-25T07:22:18.321Z
Learning: In this repo’s MDX documentation files, treat `@/...` paths as aliases that resolve to the `src/` directory (e.g., `@/assets/docs/foo/bar.png` -> `src/assets/docs/foo/bar.png`). When reviewing, do not flag `@`-prefixed image (or other asset) paths as broken; instead, verify that the corresponding physical file exists under `src/`.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-06T07:23:46.423Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 658
File: src/components/templates/agent-connectors/_section-before-tool-list-xero-common-patterns.mdx:15-63
Timestamp: 2026-05-06T07:23:46.423Z
Learning: In agentkit agent connectors documentation (files under src/components/templates/agent-connectors and src/content/docs/agentkit/connectors), do not require all four language tabs for SDK code examples. These docs may use only the language tabs relevant to the content (e.g., Node.js and Python). This is an exception to the standard multilingual guideline and should be applied consistently across connector docs.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-07T16:00:06.233Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/components/templates/agent-connectors/_section-after-setup-gmail-common-workflows.mdx:13-39
Timestamp: 2026-05-07T16:00:06.233Z
Learning: In documentation MDX files under src/components/templates/agent-connectors/ and src/content/docs/agentkit/connectors/, code examples are intentionally simplified. Do not require or flag missing error handling/failure paths (e.g., try/catch, retries, or explicit error returns) in these docs, even if the project’s general guideline expects both success and error paths in code examples.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-07T16:00:21.950Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/components/templates/agent-connectors/_section-after-setup-google_ads-common-workflows.mdx:10-18
Timestamp: 2026-05-07T16:00:21.950Z
Learning: In AgentKit agent connector documentation code examples located under src/components/templates/agent-connectors/** and src/content/docs/agentkit/connectors/** (MDX files), do not add explicit error handling in the sample code (e.g., no try/catch blocks or rejected-promise branches). These snippets are intentionally “success-path only” to keep the documentation concise, and this is an explicit exception to any general review guideline that requires both success and error paths in every code example.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

📚 Learning: 2026-05-16T17:25:30.736Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 693
File: src/content/docs/authenticate/mcp/troubleshooting.mdx:170-170
Timestamp: 2026-05-16T17:25:30.736Z
Learning: In this repo’s documentation (MD/MDX), external links should be written using plain Markdown link syntax: `[text](url)`. Do not flag external links for missing `target="_blank"` or `rel="noopener"`, and avoid converting Markdown links into raw HTML `<a>` tags just to add those attributes, since that would be inconsistent with the established doc pattern.

Applied to files:

• src/components/templates/agent-connectors/_setup-devrevmcp.mdx

🔇 Additional comments (1)

src/components/templates/agent-connectors/_setup-devrevmcp.mdx (1)

1-26: LGTM!

---

Walkthrough

Adds many new MCP connector tool registries and MDX docs, updates Figma/HubSpot/Outlook tool schemas, and registers providers in the agent-connectors catalog.

Changes

Connector documentation and tool coverage

Layer / File(s)	Summary
Catalog and new tool registries src/data/agent-connectors/catalog.ts, src/data/agent-connectors/{convertapimcp,databoxmcp,deepgrammcp,devrevmcp,docsautomatormcp,echtpostmcp,fiberymcp,fulenrichmcp,huggingfacemcp,kitmcp,lemlistmcp,mem0mcp,memberstackmcp,motionmcp,pendomcp,prismamcp,twilio,erasermcp}.ts	Adds provider entries to the catalog and new tools: Tool[] exports defining tool names, descriptions, and parameter schemas for each new connector.
Connector MDX quickstarts & docs src/content/docs/agentkit/connectors/{convertapimcp,databoxmcp,deepgrammcp,devrevmcp,docsautomatormcp,echtpostmcp,fiberymcp,fullenrichmcp,huggingfacemcp,kitmcp,lemlistmcp,mem0mcp,memberstackmcp,motionmcp,pendomcp,prismamcp,twilio,erasermcp}.mdx	Each MDX page adds frontmatter, inline heading styles, a Quickstart (SDK install tabs, credentials, OAuth first-call), a "What you can do" list, and renders the connector's ToolList.
Figma tool contract and docs updates src/data/agent-connectors/figma.ts, src/content/docs/agentkit/connectors/figma.mdx	Changes event filter shape (event_type → events), expands figma_file_get and variables update parameters (structured variableCollections/modes), adds analytics group_by requirements, and updates the docs capability bullets.
HubSpot campaign/forms/marketing email expansion src/data/agent-connectors/hubspot.ts	Adds campaign asset/revenue tools, form CRUD/submissions tools, and marketing email create/update/delete tools with expanded parameter surfaces.
Outlook event, To Do, and mail updates src/data/agent-connectors/outlook.ts, src/content/docs/agentkit/connectors/outlook.mdx	Introduces event accept/tentative tools, expands To Do/calendar/message parameter schemas, adds mail update tools, and updates the connector capability list.
Connector setup templates and exports src/components/templates/agent-connectors/_setup-devrevmcp.mdx, src/components/templates/agent-connectors/_setup-twilio.mdx, src/components/templates/agent-connectors/index.ts	Adds DevRev and Twilio setup MDX templates and re-exports them from the templates index.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• scalekit-inc/developer-docs#704: Adds connector docs and updates the connector catalog (similar provider registry edits).
• scalekit-inc/developer-docs#697: Connector additions that update docs and the catalog (related MCP connector work).
• scalekit-inc/developer-docs#735: Extends the connector catalog with MCP providers (overlapping surface).

Suggested reviewers

• ravibits
• saif-at-scalekit
• amitash1912
• AkshayParihar33

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/sync-new-connectors-jun2026

• 🛠️ fix frontmatter
• 🛠️ fix internal links

[netlify]

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	2d8e5a8
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/6a2ceb5b5a3e5800080cdb3b
😎 Deploy Preview	https://deploy-preview-748--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	f34ae25
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/6a2cf8f64c9f280008177a0a
😎 Deploy Preview	https://deploy-preview-748--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/content/docs/agentkit/connectors/twilio.mdx`:
- Around line 27-50: The quickstart for the Basic Auth Twilio connector is
missing the non-OAuth first-call step: update the Steps block in the connector
quickstart to include a third step that renders QuickstartGenericApikeySection
(after the AgentKitCredentials step) so readers see the first execute_tool call;
ensure the new step uses the non-OAuth quickstart template and references the
same credential component flow already present (AgentKitCredentials) so the page
is task-complete for Basic Auth connectors.

In `@src/data/agent-connectors/echtpostmcp.ts`:
- Around line 431-435: The tool parameter definition for the search field (the
object with name: 'search', type: 'string') currently mentions filtering by
"name or company"—remove "company" and update the description to reference the
actual motive-related fields this connector supports (e.g., filtering by motive
or motive-related fields) so the help text accurately describes what the search
term filters; edit the description string for the search parameter in the
tool/schema definition to reflect this change.

In `@src/data/agent-connectors/prismamcp.ts`:
- Around line 5-7: The connector metadata for the tool named
'prismamcp_create_prisma_postgres_backup' contains a contradictory description
(it claims "Create" in the name but says on‑demand creation is not supported);
fix the upstream sync metadata (do not hand-edit the generated file) so the
tool's description matches its actual behavior — either rename the tool to
reflect that it manages or lists automated backups or change the description to
explicitly state it only interacts with system-created automated backups (remove
the "create" implication). Update the metadata entry for the symbol
prismamcp_create_prisma_postgres_backup accordingly.

In `@src/data/agent-connectors/twilio.ts`:
- Around line 10-57: Update the Twilio tool param types to match upstream API:
in src/data/agent-connectors/twilio.ts (lines 10-57) for the tool
"twilio_available_numbers_local" change param "area_code" type from string to
integer and change "sms_enabled" and "voice_enabled" types from string to
boolean; in the same file (lines 498-531) for the tool
"twilio_available_numbers_toll_free" change "area_code" type from string to
integer; also update the Verify Service tool (referenced in the comment at lines
498-531) parameters "lookup_enabled", "psd2_enabled", and
"skip_sms_to_landlines" from string to boolean so the param types match Twilio's
lookupEnabled/psd2Enabled/skipSmsToLandlines fields.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 86dc1c44-eee3-420d-9eda-2feade985f24

📥 Commits

Reviewing files that changed from the base of the PR and between dcee972 and 1553b05.

📒 Files selected for processing (40)

• src/content/docs/agentkit/connectors/convertapimcp.mdx
• src/content/docs/agentkit/connectors/databoxmcp.mdx
• src/content/docs/agentkit/connectors/deepgrammcp.mdx
• src/content/docs/agentkit/connectors/devrevmcp.mdx
• src/content/docs/agentkit/connectors/docsautomatormcp.mdx
• src/content/docs/agentkit/connectors/echtpostmcp.mdx
• src/content/docs/agentkit/connectors/fiberymcp.mdx
• src/content/docs/agentkit/connectors/figma.mdx
• src/content/docs/agentkit/connectors/fullenrichmcp.mdx
• src/content/docs/agentkit/connectors/huggingfacemcp.mdx
• src/content/docs/agentkit/connectors/kitmcp.mdx
• src/content/docs/agentkit/connectors/lemlistmcp.mdx
• src/content/docs/agentkit/connectors/mem0mcp.mdx
• src/content/docs/agentkit/connectors/memberstackmcp.mdx
• src/content/docs/agentkit/connectors/motionmcp.mdx
• src/content/docs/agentkit/connectors/outlook.mdx
• src/content/docs/agentkit/connectors/pendomcp.mdx
• src/content/docs/agentkit/connectors/prismamcp.mdx
• src/content/docs/agentkit/connectors/twilio.mdx
• src/data/agent-connectors/catalog.ts
• src/data/agent-connectors/convertapimcp.ts
• src/data/agent-connectors/databoxmcp.ts
• src/data/agent-connectors/deepgrammcp.ts
• src/data/agent-connectors/devrevmcp.ts
• src/data/agent-connectors/docsautomatormcp.ts
• src/data/agent-connectors/echtpostmcp.ts
• src/data/agent-connectors/fiberymcp.ts
• src/data/agent-connectors/figma.ts
• src/data/agent-connectors/fullenrichmcp.ts
• src/data/agent-connectors/hubspot.ts
• src/data/agent-connectors/huggingfacemcp.ts
• src/data/agent-connectors/kitmcp.ts
• src/data/agent-connectors/lemlistmcp.ts
• src/data/agent-connectors/mem0mcp.ts
• src/data/agent-connectors/memberstackmcp.ts
• src/data/agent-connectors/motionmcp.ts
• src/data/agent-connectors/outlook.ts
• src/data/agent-connectors/pendomcp.ts
• src/data/agent-connectors/prismamcp.ts
• src/data/agent-connectors/twilio.ts