Skip to content

[No QA] [Hold for feature] Create Connect Grok to Expensify articles - #102583

Open
stephanieelliott wants to merge 2 commits into
mainfrom
helpsite-grok-connector
Open

stephanieelliott wants to merge 2 commits into
mainfrom
helpsite-grok-connector

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

Master tracking: https://github.com/Expensify/Expensify/issues/679718
Resource issue: https://github.com/Expensify/Expensify/issues/686304

Created article Connect Grok to Expensify and added Grok to master AI Assistants hub article.

Updated the description and links for connecting Grok to Expensify, enhancing clarity and providing direct access to relevant documentation.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-29T21:26:01.591779Z bd9511c PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@stephanieelliott stephanieelliott added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Sep 29, 2026
@stephanieelliott stephanieelliott changed the title Revise Grok to Expensify connection instructions [Hold for feature] Create Connect Grok to Expensify articles Sep 29, 2026
3. Remove or disconnect the Expensify MCP server connection.

You may also revoke access directly through Expensify’s OAuth revocation flow if supported by your client configuration.
You may also revoke access directly through **Device management** in your Expensify account if supported by your AI client. [Learn how to managed logged in devices](/articles/new-expensify/settings/Manage-Logged-in-Devices).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anchor text grammar / typo: "Learn how to managed logged in devices" should read "Learn how to manage logged-in devices" to match the linked article and the descriptive anchor-text standard. Also remove the trailing space at the end of the line.

- Approve reports
- Edit expenses
- Reimburse payments
- Manage Workspace settings

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Terminology / consistency: Use lowercase "workspace settings" here. The companion MCP article uses lowercase "workspace" as a common noun (e.g., "manage workspace settings"), so "Manage Workspace settings" is inconsistent.

Any member with an Expensify account and a Grok account can connect Grok to Expensify.

## How to connect Grok to Expensify

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step formatting: This is the article's primary "How to" workflow, but the instructions are prose. Per HELP_AUTHORING_GUIDELINES Section 5, procedural instructions should be sequential numbered steps. Consider converting the connect flow (open connectors, find Expensify, follow Grok's prompts to authorize) into numbered steps.

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment
This PR adds a new article, Connect Grok to Expensify, and updates the master Use the Expensify MCP server with AI assistants article to include Grok and to distinguish built-in connectors from manual MCP setup. Both files are well structured and task-oriented. The changes are strong overall, with a few style-consistency and copy issues worth fixing before merge.

Scores Summary

  • Readability: 9/10 - Clear, concise, scannable prose with well-formed capability lists and sequential numbered steps. A couple of trailing-space and bracket-spacing artifacts are the only blemishes.
  • AI Readiness: 9/10 - Complete YAML metadata including internalScope and search-aligned keywords on both files. Headings are task-based, the hierarchy is limited to top-level and second-level headings plus the exempt FAQ heading, and each article includes full 'How to connect ... to Expensify' headings using the feature name.
  • Style Compliance: 6/10 - The modified MCP article lowercases Workspace to workspace in three places (permissions/settings), conflicting with the naming conventions and with the new Grok article that correctly uses Workspace settings. There is also a typo in new anchor text.

Key Findings

  • Terminology regression: In the MCP article diff, Workspace permissions and Workspace settings were changed to lowercase workspace. Workspace is an exact product term and should retain its capitalization; this also creates inconsistency with the new Grok article.
  • Typo in new anchor text: 'Learn how to managed logged in devices' should read 'Learn how to manage logged-in devices'.
  • Minor formatting artifacts: trailing whitespace on the new Device management line and on a couple of Grok lines; the Grok custom-connector link has a stray space inside the bracket 'Add a custom MCP connector '.
  • Positive: Excellent internalScope and keyword coverage, clean task-based headings, question-style FAQ entries, good use of relative internal cross-links (e.g., Manage-Logged-in-Devices), and helpful removal of the duplicated FAQ at the end of the MCP article.
  • Positive: Grok article correctly scopes read-only capabilities (can/cannot lists) and mirrors the established pattern of the sibling connector articles.

Recommendations

  • Restore Workspace capitalization in the MCP article (Workspace permissions, Workspace settings in both the security section and the FAQ answer) to comply with naming conventions and match the Grok article.
  • Fix the 'managed' to 'manage' typo and consider 'logged-in' hyphenation in the new anchor text.
  • Remove trailing whitespace and the stray space inside the 'Add a custom MCP connector ' link text.
  • Confirm the MCP server URL trailing-slash change (/mcp/) is intentional and consistent across all connector articles.

Files Reviewed

  • docs/articles/new-expensify/connections/connect-ai-assistants/Connect-Grok-to-Expensify.md (new) - Strong; minor whitespace/bracket cleanup only.
  • docs/articles/new-expensify/connections/connect-ai-assistants/Use-the-Expensify-MCP-Server-With-AI-Assistants.md (modified) - Good restructuring; fix Workspace casing and the anchor-text typo.

Note: Detailed line-by-line feedback has been provided as inline comments.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bd9511cc5d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

## Which AI assistants work with Expensify’s MCP server?

Any MCP-compatible AI client may work with Expensify’s MCP server. Official setup guides are available for Claude, ChatGPT and Cursor.
ChatGPT, Claude, Cursor, and Grok can connect to Expensify using their built-in Expensify integrations.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish custom MCP setups from built-in integrations

This incorrectly says all four clients have built-in Expensify integrations. The linked Claude guide explicitly requires users to add a custom connector and enter the MCP URL (Connect-Claude-to-Expensify-Using-MCP.md, lines 25–34), while the Cursor guide offers an MCP install link or manual server configuration (Connect-Cursor-to-Expensify-Using-MCP.md, lines 29–39). Users may therefore look for nonexistent built-in integrations; classify each client according to its actual setup flow instead.

Useful? React with 👍 / 👎.

@github-actions github-actions Bot changed the title [Hold for feature] Create Connect Grok to Expensify articles [No QA] [Hold for feature] Create Connect Grok to Expensify articles Sep 29, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants