Add roles and custom claims support to MCP BYOA by AkshayParihar33 · Pull Request #577 · scalekit-inc/developer-docs

AkshayParihar33 · 2026-04-08T15:14:46Z

Summary

This PR adds support for roles and custom claims in the MCP BYOA (Bring Your Own Authentication) connector implementation.

Changes

Added roles and custom attributes documentation in MCP BYOA reference
Fixed broken relative link in granolamcp connector page

Test plan

Preview link displays correctly
All internal links resolve properly
Content renders without formatting issues

Summary by CodeRabbit

Documentation
- Updated authentication docs: cURL example now shows optional user claims — added a roles array and custom_attributes fields to illustrate extra attributes in the request payload.
- Improved agent connector docs: corrected formatting/wording for inline citations to enhance clarity while preserving the documented behavior and required-field guidance.

coderabbitai · 2026-04-08T15:15:04Z

Walkthrough

Updated two documentation pages: the custom-auth cURL example now includes optional user claims (roles and custom_attributes), and a minor formatting/spacing fix was made in the Granola MCP agent connectors reference text.

Changes

Cohort / File(s)	Summary
MCP Authentication Documentation `src/content/docs/mcp/auth-methods/custom-auth.mdx`	Updated cURL example JSON payload to add optional user claims: a `roles` array (`["support","developer"]`) and a `custom_attributes` object containing `access_level` and `subscription_type`, alongside existing `sub` and `email` fields.
Agent Connectors Reference `src/content/docs/reference/agent-connectors/granolamcp.mdx`	Removed a formatting/spacing artifact in descriptive text for `granolamcp_query_granola_meetings`; no parameter or behavioral changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Adding granola mcp provider docs #531: Modifies src/content/docs/reference/agent-connectors/granolamcp.mdx — related to the same connector reference file.
Updated MCP Overview page with smaller breakdown pages and updated BYOA Page #423: Edits src/content/docs/mcp/auth-methods/custom-auth.mdx — overlaps changes to the custom-auth documentation.

Suggested reviewers

saif-at-scalekit
ravibits
amitash1912

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add roles and custom claims support to MCP BYOA' is directly related to the main change in the changeset, which updates the cURL example to include roles and custom_attributes fields in the MCP auth methods documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch preview/mcp-byoa-roles-custom-claims

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/content/docs/mcp/auth-methods/custom-auth.mdx`:
- Around line 207-212: Add a short security note immediately above or below the
JSON example that warns that the "roles" and "custom_attributes" claims in the
example are security-sensitive and must be populated only by your trusted
backend identity provider (not from client input); briefly state the threat
(users can tamper with client-supplied claims to escalate privileges), why the
pattern is required (server-side signing/validation of claims ensures
integrity), and what can go wrong if omitted (privilege escalation and
unauthorized access). Reference the exact fields "roles" and "custom_attributes"
in the note so readers can map the warning to the example.
- Around line 207-212: The cURL example shows extra optional claims "roles" and
"custom_attributes" but the Python/Node/Go SDK snippets do not — update the BYOA
payload in the Python, Node, and Go snippets within custom-auth.mdx to include
the same "roles": ["support","developer"] and "custom_attributes": {
"access_level": 101, "subscription_type": "PREMIUM" } fields (using the same
keys/values and terminology as the cURL example) so all tabs present an
identical example payload model for the BYOA flow.

In `@src/content/docs/reference/agent-connectors/granolamcp.mdx`:
- Line 90: The tool description sentence starting "Query Granola about the
user's meetings using natural language..." contains the ambiguous phrase "inline
citation links in mark"; update that phrase to a precise term such as "inline
citation links in Markdown" (or other chosen unambiguous format) so the full
sentence reads e.g. "Returns a tailored response with inline citation links in
Markdown that reference source meeting notes." Locate and replace the exact
phrase "inline citation links in mark" in the agent connector description to
ensure clear, consistent documentation terminology.

🪄 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: 2a3c2874-0797-485d-b064-a62e572d8a32

📥 Commits

Reviewing files that changed from the base of the PR and between 447ad4a and 1e0adf8.

📒 Files selected for processing (2)

src/content/docs/mcp/auth-methods/custom-auth.mdx
src/content/docs/reference/agent-connectors/granolamcp.mdx

📜 Review details

🧰 Additional context used

📓 Path-based instructions (4)

**/*.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/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.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).

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: frontmatter link, a <LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.

Code examples

ALL code examples that show SDK usage MUST include all four language
tabs...

Files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.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/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.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/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

src/content/docs/**/*.mdx

📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)

src/content/docs/**/*.mdx: In MDX documentation files, <Steps> must contain one continuous ordered list. Wrap <Steps> around a normal Markdown ordered list such as 1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the 1. ##, 2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images, <Tabs>, <TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside <Steps>. If the content is mostly <Tabs> or other JSX-heavy blocks, use normal section headings instead of <Steps>
In MDX documentation files, when <Tabs> is used inside a step, keep <Tabs>, <TabItem>, </TabItem>, and </Tabs> consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside </Steps>

Files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

🧠 Learnings (29)

📓 Common learnings

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs in general), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication documentation in Agent Auth connection-type sections.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs generally), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication connection type documentation in Agent Auth connection-type sections.

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Keep documentation accurate and up-to-date with product changes, updating examples when APIs change

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Product-based documentation (MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, Modular SSO) MUST follow a journey-focused approach

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:55.583Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, the parameter tables (showing tool properties) are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Any table format corrections must be made in the generation script, not by manually editing the generated MDX files. The script should be updated to output the required "Name | Type | Required | Description" four-column table format per coding guidelines.

📚 Learning: 2026-02-26T07:22:49.128Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T15:59:51.911Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48
Timestamp: 2026-03-25T15:59:51.911Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files (agent-connector usage templates, e.g., `_usage-granolamcp.mdx`), code examples are intentionally directional/illustrative and are meant to show the call sequence pattern rather than production-ready runnable code. Do not flag the absence of try/except or try/catch error handling in these usage template files.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:23:24.179Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:44:16.883Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:16.883Z
Learning: In MDX files under src/content/docs/reference/agent-connectors, specifically simple connector-header div blocks used for the header grid layout (e.g., a 5-column grid with description and logo), treat the absence of a justification comment as acceptable/readable. Do not flag or require a justification comment for these simple header div blocks in agent-connector reference pages.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T16:00:25.846Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/content/docs/reference/agent-connectors/granolamcp.mdx:52-58
Timestamp: 2026-03-25T16:00:25.846Z
Learning: For MDX pages under src/content/docs/reference/agent-connectors/ (e.g., agent-connector reference pages like granolamcp.mdx), if you have a short sequential setup procedure of 4 items or fewer, it’s acceptable to use a plain Markdown numbered list instead of the Starlight <Steps> component. This exception is intended to avoid visual clutter on pages that already contain multiple structured content blocks (such as tables, <details>/<summary>, or tool sections). When this 4-or-fewer condition is met, do not flag missing/avoided <Steps> for these setup procedures.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:21:32.951Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:20:42.107Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-04-01T10:25:46.962Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 567
File: src/content/docs/reference/agent-connectors/apifymcp.mdx:70-70
Timestamp: 2026-04-01T10:25:46.962Z
Learning: For agent-connector reference documentation pages (MDX under `src/content/docs/reference/agent-connectors/`), treat backtick/code-quoted example search terms inside parameter tables (e.g., `"google maps"`, `"instagram scraper"`) as literal query inputs that users type. Do not flag changes to the lowercase casing of words within these code-quoted example queries as if they were improper product-name capitalization; the casing is intentional to reflect realistic user input.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T10:15:02.544Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 529
File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190
Timestamp: 2026-03-25T10:15:02.544Z
Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Maintain consistent terminology across documentation pages

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-30T18:18:50.883Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-02-04T12:47:16.544Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-02-25T08:57:12.201Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-02-25T13:04:27.491Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-05T11:29:08.125Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 463
File: src/content/docs/agent-auth/providers.mdx:35-73
Timestamp: 2026-03-05T11:29:08.125Z
Learning: In src/content/docs/agent-auth/providers.mdx, the Card components intentionally use icon=" " (a space) to render consistent colored boxes since some Starlight icon names resolve to icons and others do not. Do not flag icon=" " as a placeholder issue for this file; treat this as a deliberate UX choice specific to this MDX page and avoid raising a placeholder-icon warning here.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-09T07:27:56.794Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 469
File: src/content/docs/guides/integrations/scim-integrations/azure-scim.mdx:95-107
Timestamp: 2026-03-09T07:27:56.794Z
Learning: Do not enforce the 3-space indentation rule for Steps component content as a hard style rule in MDX files under src/content/docs/**/*.mdx. Only flag/rectify it if it causes visible rendering problems in the UI. Otherwise, allow current formatting; apply this rule only when rendering issues are observed and document any fixes.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-09T07:32:38.426Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 467
File: src/content/docs/sso/guides/sso-user-attributes.mdx:108-148
Timestamp: 2026-03-09T07:32:38.426Z
Learning: In MDX code samples under src/content/docs (and similar conceptual snippets in scalekit-inc/developer-docs), when an example's sole purpose is to show how to access a specific value (e.g., reading JWT claims after token validation), omit error/non-happy-path handling to keep the snippet focused. Do not flag the absence of error paths in narrowly scoped conceptual snippets.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-17T16:01:50.487Z

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 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/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.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/content/docs/reference/agent-connectors/granolamcp.mdx
src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-02-26T07:18:41.518Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-03T13:35:47.638Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:47.638Z
Learning: In Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), only Python SDK examples for Agent Actions/Agent Connectors should be required for now. Do not enforce or require multi-language SDK code examples (Node.js, Python, Go, Java) until the respective SDKs support Agent Actions. Once supported, you can add and require other languages in those docs. This guideline applies to all files under the agent-connectors documentation path.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:51:40.660Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:40.660Z
Learning: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/ (e.g., https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg). The host should be cdn.scalekit.com (not cdn.scalekit.cloud). Do not flag or modify image src attributes that already use cdn.scalekit.com for provider icons within this directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-10T05:32:59.967Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 424
File: public/api/scalekit.scalar.json:3451-3457
Timestamp: 2026-02-10T05:32:59.967Z
Learning: In scalekit-inc/developer-docs, the file public/api/scalekit.scalar.json is a generated OpenAPI artifact; reviewers should avoid direct edits. For inconsistencies (e.g., the /api/v1/permissions "type" query param description vs. enum), handle short-term via release/PR notes and track long-term fixes in the generator or source templates rather than modifying the generated JSON.

Applied to files:

src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-12T05:02:13.454Z

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs in general), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication documentation in Agent Auth connection-type sections.

Applied to files:

src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-03-12T05:02:13.454Z

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs generally), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication connection type documentation in Agent Auth connection-type sections.

Applied to files:

src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Use present tense for descriptions: 'Scalekit handles the complex authentication flow', 'The SDK provides methods to refresh tokens'

Applied to files:

src/content/docs/mcp/auth-methods/custom-auth.mdx

📚 Learning: 2026-02-02T05:55:51.251Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/native-app.mdx:72-179
Timestamp: 2026-02-02T05:55:51.251Z
Learning: In the `src/content/docs/authenticate/fsa/multiapp/` directory, the multi-app authentication documentation (native-app.mdx, single-page-app.mdx, web-app.mdx, overview.mdx) currently uses conceptual shell/curl examples instead of multi-language SDK code examples because the Scalekit SDKs have not yet been built/updated for multi-app functionality. Once the SDKs are ready, these files should be updated to include all 4 languages (Node.js, Python, Go, Java) using `<Tabs syncKey="tech-stack">`.

Applied to files:

src/content/docs/mcp/auth-methods/custom-auth.mdx

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/content/docs/reference/agent-connectors/granolamcp.mdx`:
- Line 90: Update the sentence "Query Granola about the user's meetings using
natural language. Returns a tailored response with inline citation that
reference source meeting notes." to fix subject-verb agreement and improve
clarity by changing "inline citation that reference" to "inline citations that
reference source meeting notes" (locate the sentence starting "Query Granola
about the user's meetings..." in the granolamcp tool description and replace the
phrase "inline citation that reference" accordingly).

🪄 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: 005dd732-67bf-4ff7-b639-a7b9d12c41ed

📥 Commits

Reviewing files that changed from the base of the PR and between 1e0adf8 and a349f52.

📒 Files selected for processing (1)

src/content/docs/reference/agent-connectors/granolamcp.mdx

📜 Review details

🧰 Additional context used

📓 Path-based instructions (4)

**/*.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/content/docs/reference/agent-connectors/granolamcp.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).

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: frontmatter link, a <LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.

Code examples

ALL code examples that show SDK usage MUST include all four language
tabs...

Files:

src/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.mdx

src/content/docs/**/*.mdx

📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)

src/content/docs/**/*.mdx: In MDX documentation files, <Steps> must contain one continuous ordered list. Wrap <Steps> around a normal Markdown ordered list such as 1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the 1. ##, 2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images, <Tabs>, <TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside <Steps>. If the content is mostly <Tabs> or other JSX-heavy blocks, use normal section headings instead of <Steps>
In MDX documentation files, when <Tabs> is used inside a step, keep <Tabs>, <TabItem>, </TabItem>, and </Tabs> consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside </Steps>

Files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

🧠 Learnings (35)

📓 Common learnings

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 577
File: src/content/docs/mcp/auth-methods/custom-auth.mdx:207-212
Timestamp: 2026-04-08T15:23:37.114Z
Learning: In `src/content/docs/mcp/auth-methods/custom-auth.mdx` (BYOA MCP custom auth, MCP section), the `roles` and `custom_attributes` fields in the `updateLoginUserDetails` / Update Login User Details call are not yet supported in the Python, Node.js, and Go SDKs. These fields currently appear only in the cURL tab example. Do not require or flag the absence of `roles` and `custom_attributes` in the Python/Node.js/Go SDK snippets until the SDKs are updated to support these fields.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs in general), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication documentation in Agent Auth connection-type sections.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs generally), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication connection type documentation in Agent Auth connection-type sections.

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Product-based documentation (MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, Modular SSO) MUST follow a journey-focused approach

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Keep documentation accurate and up-to-date with product changes, updating examples when APIs change

📚 Learning: 2026-02-26T07:23:24.179Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:44:16.883Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:16.883Z
Learning: In MDX files under src/content/docs/reference/agent-connectors, specifically simple connector-header div blocks used for the header grid layout (e.g., a 5-column grid with description and logo), treat the absence of a justification comment as acceptable/readable. Do not flag or require a justification comment for these simple header div blocks in agent-connector reference pages.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:22:49.128Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:21:32.951Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T16:00:25.846Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/content/docs/reference/agent-connectors/granolamcp.mdx:52-58
Timestamp: 2026-03-25T16:00:25.846Z
Learning: For MDX pages under src/content/docs/reference/agent-connectors/ (e.g., agent-connector reference pages like granolamcp.mdx), if you have a short sequential setup procedure of 4 items or fewer, it’s acceptable to use a plain Markdown numbered list instead of the Starlight <Steps> component. This exception is intended to avoid visual clutter on pages that already contain multiple structured content blocks (such as tables, <details>/<summary>, or tool sections). When this 4-or-fewer condition is met, do not flag missing/avoided <Steps> for these setup procedures.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T10:15:02.544Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 529
File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190
Timestamp: 2026-03-25T10:15:02.544Z
Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:20:42.107Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T15:59:51.911Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48
Timestamp: 2026-03-25T15:59:51.911Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files (agent-connector usage templates, e.g., `_usage-granolamcp.mdx`), code examples are intentionally directional/illustrative and are meant to show the call sequence pattern rather than production-ready runnable code. Do not flag the absence of try/except or try/catch error handling in these usage template files.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-04-01T10:25:46.962Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 567
File: src/content/docs/reference/agent-connectors/apifymcp.mdx:70-70
Timestamp: 2026-04-01T10:25:46.962Z
Learning: For agent-connector reference documentation pages (MDX under `src/content/docs/reference/agent-connectors/`), treat backtick/code-quoted example search terms inside parameter tables (e.g., `"google maps"`, `"instagram scraper"`) as literal query inputs that users type. Do not flag changes to the lowercase casing of words within these code-quoted example queries as if they were improper product-name capitalization; the casing is intentional to reflect realistic user input.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:18:41.518Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Use descriptive link text and avoid 'click here' in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Maintain consistent terminology across documentation pages

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Don't use inconsistent terminology across documentation pages

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Don't use overly technical jargon without explanation in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-16T21:02:51.181Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/expressive-code.mdc:0-0
Timestamp: 2026-03-16T21:02:51.181Z
Learning: Applies to **/*.{md,mdx} : Use Expressive Code consistently across all documentation pages, preferring Starlight's `<Code>` component for rich features (titles, markers, accurate syntax highlighting) and dynamic snippets

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Use backticks for code, file names, CLI flags, and endpoints in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-27T17:20:14.679Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Applies to **/*.{md,mdx} : Use meaningful link text; never use 'click here' or 'this' as link labels. 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

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

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

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:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T04:24:59.653Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 0
File: :0-0
Timestamp: 2026-03-13T04:24:59.653Z
Learning: In scalekit-inc/developer-docs, for PRs focused on tooling and templatizing (e.g., extracting usage sections into reusable MDX templates and updating sync scripts), review comments about .mdx file content quality (casing, unused imports, import consolidation, endpoint descriptions, etc.) are considered out of scope and should be resolved without blocking the PR.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-05T11:29:08.125Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 463
File: src/content/docs/agent-auth/providers.mdx:35-73
Timestamp: 2026-03-05T11:29:08.125Z
Learning: In src/content/docs/agent-auth/providers.mdx, the Card components intentionally use icon=" " (a space) to render consistent colored boxes since some Starlight icon names resolve to icons and others do not. Do not flag icon=" " as a placeholder issue for this file; treat this as a deliberate UX choice specific to this MDX page and avoid raising a placeholder-icon warning here.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

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

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:35.371Z
Learning: In `src/components/templates/agent-connectors/_setup-*.mdx` files, empty alt text `![]()` for redirect URI screenshots (e.g., `use-own-credentials-redirect-uri.png`) is a deliberate and consistent pattern across all connector setup template files. Do not flag missing alt text on these images in future reviews of files under `src/components/templates/agent-connectors/`.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-30T18:18:50.883Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-04T12:47:16.544Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-25T08:57:12.201Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-25T13:04:27.491Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-09T07:27:56.794Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 469
File: src/content/docs/guides/integrations/scim-integrations/azure-scim.mdx:95-107
Timestamp: 2026-03-09T07:27:56.794Z
Learning: Do not enforce the 3-space indentation rule for Steps component content as a hard style rule in MDX files under src/content/docs/**/*.mdx. Only flag/rectify it if it causes visible rendering problems in the UI. Otherwise, allow current formatting; apply this rule only when rendering issues are observed and document any fixes.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-09T07:32:38.426Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 467
File: src/content/docs/sso/guides/sso-user-attributes.mdx:108-148
Timestamp: 2026-03-09T07:32:38.426Z
Learning: In MDX code samples under src/content/docs (and similar conceptual snippets in scalekit-inc/developer-docs), when an example's sole purpose is to show how to access a specific value (e.g., reading JWT claims after token validation), omit error/non-happy-path handling to keep the snippet focused. Do not flag the absence of error paths in narrowly scoped conceptual snippets.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-17T16:01:50.487Z

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 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/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-03T13:35:47.638Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:47.638Z
Learning: In Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), only Python SDK examples for Agent Actions/Agent Connectors should be required for now. Do not enforce or require multi-language SDK code examples (Node.js, Python, Go, Java) until the respective SDKs support Agent Actions. Once supported, you can add and require other languages in those docs. This guideline applies to all files under the agent-connectors documentation path.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:51:40.660Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:40.660Z
Learning: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/ (e.g., https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg). The host should be cdn.scalekit.com (not cdn.scalekit.cloud). Do not flag or modify image src attributes that already use cdn.scalekit.com for provider icons within this directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

netlify · 2026-04-08T15:33:54Z

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	`8ba314f`
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/69d67ad85171dd00083d6339
😎 Deploy Preview	https://deploy-preview-577--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

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

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

src/content/docs/reference/agent-connectors/granolamcp.mdx (2)
16-16: 🧹 Nitpick | 🔵 Trivial

Remove unused Code import to reduce bundle size.

The Code component is imported but never used in this file. The file uses only fenced code blocks (```), which don't require the import.
♻️ Proposed fix
-import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components'
+import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside } from '@astrojs/starlight/components'
Based on learnings: Import Code from astrojs/starlight/components only if the MDX content actually uses the <Code> component to avoid unnecessary imports and reduce bundle size.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/reference/agent-connectors/granolamcp.mdx` at line 16,
Remove the unused Code import from the top-level import list to avoid shipping
dead code: edit the import statement that currently reads "import { Card,
CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } ..." and drop "Code" so
only actually used components (Card, CardGrid, Tabs, TabItem, Badge, Steps,
Aside) are imported.
25-25: 🧹 Nitpick | 🔵 Trivial

Update CDN host for provider icon to match guidelines.

The provider icon uses cdn.scalekit.cloud but should use cdn.scalekit.com for consistency with the standard CDN host for provider icons.
🔧 Proposed fix
-  <img src="https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/granola.svg" width="64" height="64" alt="Granola MCP logo" />
+  <img src="https://cdn.scalekit.com/sk-connect/assets/provider-icons/granola.svg" width="64" height="64" alt="Granola MCP logo" />
As per coding guidelines: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/reference/agent-connectors/granolamcp.mdx` at line 25, The
provider icon <img src="...granola.svg" /> uses the wrong CDN host; update the
src host from cdn.scalekit.cloud to the standard cdn.scalekit.com so the URL
becomes https://cdn.scalekit.com/sk-connect/assets/provider-icons/granola.svg;
ensure the filename and path (/sk-connect/assets/provider-icons/granola.svg)
remain unchanged in the img tag to conform to the provider-icons CDN guideline.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@src/content/docs/reference/agent-connectors/granolamcp.mdx`:
- Line 16: Remove the unused Code import from the top-level import list to avoid
shipping dead code: edit the import statement that currently reads "import {
Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } ..." and drop "Code"
so only actually used components (Card, CardGrid, Tabs, TabItem, Badge, Steps,
Aside) are imported.
- Line 25: The provider icon <img src="...granola.svg" /> uses the wrong CDN
host; update the src host from cdn.scalekit.cloud to the standard
cdn.scalekit.com so the URL becomes
https://cdn.scalekit.com/sk-connect/assets/provider-icons/granola.svg; ensure
the filename and path (/sk-connect/assets/provider-icons/granola.svg) remain
unchanged in the img tag to conform to the provider-icons CDN guideline.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: b70b0fee-eef7-4421-b738-1143e1256e23

📥 Commits

Reviewing files that changed from the base of the PR and between a349f52 and 8ba314f.

📒 Files selected for processing (1)

src/content/docs/reference/agent-connectors/granolamcp.mdx

📜 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 (4)

**/*.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/content/docs/reference/agent-connectors/granolamcp.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).

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: frontmatter link, a <LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.

Code examples

ALL code examples that show SDK usage MUST include all four language
tabs...

Files:

src/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.mdx

src/content/docs/**/*.mdx

📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)

src/content/docs/**/*.mdx: In MDX documentation files, <Steps> must contain one continuous ordered list. Wrap <Steps> around a normal Markdown ordered list such as 1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the 1. ##, 2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images, <Tabs>, <TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside <Steps>. If the content is mostly <Tabs> or other JSX-heavy blocks, use normal section headings instead of <Steps>
In MDX documentation files, when <Tabs> is used inside a step, keep <Tabs>, <TabItem>, </TabItem>, and </Tabs> consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside </Steps>

Files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

🧠 Learnings (36)

📓 Common learnings

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 577
File: src/content/docs/mcp/auth-methods/custom-auth.mdx:207-212
Timestamp: 2026-04-08T15:23:37.114Z
Learning: In `src/content/docs/mcp/auth-methods/custom-auth.mdx` (BYOA MCP custom auth, MCP section), the `roles` and `custom_attributes` fields in the `updateLoginUserDetails` / Update Login User Details call are not yet supported in the Python, Node.js, and Go SDKs. These fields currently appear only in the cURL tab example. Do not require or flag the absence of `roles` and `custom_attributes` in the Python/Node.js/Go SDK snippets until the SDKs are updated to support these fields.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs in general), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication documentation in Agent Auth connection-type sections.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs generally), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication connection type documentation in Agent Auth connection-type sections.

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Product-based documentation (MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, Modular SSO) MUST follow a journey-focused approach

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Keep documentation accurate and up-to-date with product changes, updating examples when APIs change

📚 Learning: 2026-02-26T07:23:24.179Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:44:16.883Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:16.883Z
Learning: In MDX files under src/content/docs/reference/agent-connectors, specifically simple connector-header div blocks used for the header grid layout (e.g., a 5-column grid with description and logo), treat the absence of a justification comment as acceptable/readable. Do not flag or require a justification comment for these simple header div blocks in agent-connector reference pages.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:22:49.128Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:21:32.951Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T16:00:25.846Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/content/docs/reference/agent-connectors/granolamcp.mdx:52-58
Timestamp: 2026-03-25T16:00:25.846Z
Learning: For MDX pages under src/content/docs/reference/agent-connectors/ (e.g., agent-connector reference pages like granolamcp.mdx), if you have a short sequential setup procedure of 4 items or fewer, it’s acceptable to use a plain Markdown numbered list instead of the Starlight <Steps> component. This exception is intended to avoid visual clutter on pages that already contain multiple structured content blocks (such as tables, <details>/<summary>, or tool sections). When this 4-or-fewer condition is met, do not flag missing/avoided <Steps> for these setup procedures.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:20:42.107Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T15:59:51.911Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48
Timestamp: 2026-03-25T15:59:51.911Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files (agent-connector usage templates, e.g., `_usage-granolamcp.mdx`), code examples are intentionally directional/illustrative and are meant to show the call sequence pattern rather than production-ready runnable code. Do not flag the absence of try/except or try/catch error handling in these usage template files.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-25T10:15:02.544Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 529
File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190
Timestamp: 2026-03-25T10:15:02.544Z
Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-04-01T10:25:46.962Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 567
File: src/content/docs/reference/agent-connectors/apifymcp.mdx:70-70
Timestamp: 2026-04-01T10:25:46.962Z
Learning: For agent-connector reference documentation pages (MDX under `src/content/docs/reference/agent-connectors/`), treat backtick/code-quoted example search terms inside parameter tables (e.g., `"google maps"`, `"instagram scraper"`) as literal query inputs that users type. Do not flag changes to the lowercase casing of words within these code-quoted example queries as if they were improper product-name capitalization; the casing is intentional to reflect realistic user input.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Maintain consistent terminology across documentation pages

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Use descriptive link text and avoid 'click here' in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Don't use inconsistent terminology across documentation pages

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.{md,mdx} : Don't use overly technical jargon without explanation in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-16T21:02:51.181Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/expressive-code.mdc:0-0
Timestamp: 2026-03-16T21:02:51.181Z
Learning: Applies to **/*.{md,mdx} : Use Expressive Code consistently across all documentation pages, preferring Starlight's `<Code>` component for rich features (titles, markers, accurate syntax highlighting) and dynamic snippets

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Use backticks for code, file names, CLI flags, and endpoints in documentation

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-27T17:20:14.679Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Applies to **/*.{md,mdx} : Use meaningful link text; never use 'click here' or 'this' as link labels. 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

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-27T17:20:14.679Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-27T17:20:14.679Z
Learning: Applies to **/*.{md,mdx} : Maintain neutral, professional tone. Avoid hype, slang, and filler words like 'simply', 'just', 'obviously'. Use the same terms throughout a page; prefer standard names over synonyms. Explain security implications when relevant

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T04:24:59.653Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 0
File: :0-0
Timestamp: 2026-03-13T04:24:59.653Z
Learning: In scalekit-inc/developer-docs, for PRs focused on tooling and templatizing (e.g., extracting usage sections into reusable MDX templates and updating sync scripts), review comments about .mdx file content quality (casing, unused imports, import consolidation, endpoint descriptions, etc.) are considered out of scope and should be resolved without blocking the PR.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.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/content/docs/reference/agent-connectors/granolamcp.mdx

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

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:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-05T11:29:08.125Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 463
File: src/content/docs/agent-auth/providers.mdx:35-73
Timestamp: 2026-03-05T11:29:08.125Z
Learning: In src/content/docs/agent-auth/providers.mdx, the Card components intentionally use icon=" " (a space) to render consistent colored boxes since some Starlight icon names resolve to icons and others do not. Do not flag icon=" " as a placeholder issue for this file; treat this as a deliberate UX choice specific to this MDX page and avoid raising a placeholder-icon warning here.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

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

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:35.371Z
Learning: In `src/components/templates/agent-connectors/_setup-*.mdx` files, empty alt text `![]()` for redirect URI screenshots (e.g., `use-own-credentials-redirect-uri.png`) is a deliberate and consistent pattern across all connector setup template files. Do not flag missing alt text on these images in future reviews of files under `src/components/templates/agent-connectors/`.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-13T12:47:52.148Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/deno-docs-style.mdc:0-0
Timestamp: 2026-01-13T12:47:52.148Z
Learning: Applies to **/*.{md,mdx} : Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-01-30T18:18:50.883Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-04T12:47:16.544Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-25T08:57:12.201Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-25T13:04:27.491Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-09T07:27:56.794Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 469
File: src/content/docs/guides/integrations/scim-integrations/azure-scim.mdx:95-107
Timestamp: 2026-03-09T07:27:56.794Z
Learning: Do not enforce the 3-space indentation rule for Steps component content as a hard style rule in MDX files under src/content/docs/**/*.mdx. Only flag/rectify it if it causes visible rendering problems in the UI. Otherwise, allow current formatting; apply this rule only when rendering issues are observed and document any fixes.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-09T07:32:38.426Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 467
File: src/content/docs/sso/guides/sso-user-attributes.mdx:108-148
Timestamp: 2026-03-09T07:32:38.426Z
Learning: In MDX code samples under src/content/docs (and similar conceptual snippets in scalekit-inc/developer-docs), when an example's sole purpose is to show how to access a specific value (e.g., reading JWT claims after token validation), omit error/non-happy-path handling to keep the snippet focused. Do not flag the absence of error paths in narrowly scoped conceptual snippets.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-17T16:01:50.487Z

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 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/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-02-26T07:18:41.518Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-03T13:35:47.638Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:47.638Z
Learning: In Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), only Python SDK examples for Agent Actions/Agent Connectors should be required for now. Do not enforce or require multi-language SDK code examples (Node.js, Python, Go, Java) until the respective SDKs support Agent Actions. Once supported, you can add and require other languages in those docs. This guideline applies to all files under the agent-connectors documentation path.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

📚 Learning: 2026-03-13T03:51:40.660Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:40.660Z
Learning: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/ (e.g., https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg). The host should be cdn.scalekit.com (not cdn.scalekit.cloud). Do not flag or modify image src attributes that already use cdn.scalekit.com for provider icons within this directory.

Applied to files:

src/content/docs/reference/agent-connectors/granolamcp.mdx

🔇 Additional comments (1)

src/content/docs/reference/agent-connectors/granolamcp.mdx (1)

90-90: LGTM — Grammar and clarity improved.

The updated wording "inline citations that reference source meeting notes" is grammatically correct and unambiguous. This successfully addresses the past review comments regarding the subject-verb agreement issue.

AkshayParihar33 added 2 commits April 8, 2026 13:14

adding roles and custom attributes in mcp byoa

d42ff59

fixing url

1e0adf8

AkshayParihar33 requested review from amitash1912, ravibits and saif-at-scalekit as code owners April 8, 2026 15:14

coderabbitai Bot requested changes Apr 8, 2026

View reviewed changes

Comment thread src/content/docs/mcp/auth-methods/custom-auth.mdx

Comment thread src/content/docs/reference/agent-connectors/granolamcp.mdx Outdated

updates

a349f52

coderabbitai Bot approved these changes Apr 8, 2026

View reviewed changes

coderabbitai Bot requested changes Apr 8, 2026

View reviewed changes

Comment thread src/content/docs/reference/agent-connectors/granolamcp.mdx Outdated

amitash1912 approved these changes Apr 8, 2026

View reviewed changes

Update src/content/docs/reference/agent-connectors/granolamcp.mdx

8ba314f

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

coderabbitai Bot approved these changes Apr 8, 2026

View reviewed changes

coderabbitai Bot reviewed Apr 8, 2026

View reviewed changes

AkshayParihar33 merged commit ff3390d into main Apr 9, 2026
4 checks passed

coderabbitai Bot mentioned this pull request Apr 22, 2026

Add MCP provider support to bring-your-own-connector #623

Merged

saif-at-scalekit deleted the preview/mcp-byoa-roles-custom-claims branch May 7, 2026 10:16

Conversation

AkshayParihar33 commented Apr 8, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Test plan

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

netlify Bot commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for scalekit-starlight ready!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

AkshayParihar33 commented Apr 8, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Apr 8, 2026 •

edited

Loading

netlify Bot commented Apr 8, 2026 •

edited

Loading