feat: add Previly personal finance MCP server

[armandleopold]

New Plugin: Previly - Personal Finance Assistant

Identifier: previly-finance
MCP Endpoint: https://app.previly.com/mcp
Website: previly.com

Description

Previly is a personal finance SaaS with an integrated AI agent. The MCP server exposes 33 tools:

• Transactions & spending analysis
• Budget management (CRUD)
• Net worth / patrimoine tracking
• Recurring payments detection
• 12-month cash flow forecasting
• Full double-entry accounting (French PCG)
• French tax declarations (IR/IS/TVA) with auto-prefill

Auth: OAuth 2.1 (Clerk)
Transport: Streamable HTTP

Summary by Sourcery

New Features:

• Introduce the previly-finance MCP server configuration for the Previly personal finance SaaS.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new MCP plugin configuration for the Previly personal finance assistant, wiring it into the project as a JSON manifest that describes its endpoint, capabilities, and auth/transport details.

File-Level Changes

Change	Details	Files
Introduce Previly personal finance MCP server manifest so the tool can be discovered and used by the host.	Add a new JSON manifest defining the previly-finance MCP server identifier and display metadata Configure the MCP HTTP endpoint to https://app.previly.com/mcp with streamable HTTP transport Document high-level capabilities such as transactions analysis, budgeting, net worth tracking, recurring payments detection, cash flow forecasting, accounting, and French tax declarations Set OAuth 2.1 (Clerk) as the authentication method for connecting to the service	src/previly-finance.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since this server uses OAuth 2.1 via Clerk, consider explicitly documenting in the JSON manifest the exact auth flow details (auth URL, token URL, scopes, and required headers) so client implementations don’t have to guess how to obtain and attach credentials.
• With 33 tools exposed, it may be worth grouping or namespacing related tools (e.g., budgeting, tax, accounting) in the manifest and ensuring their names/descriptions are narrowly scoped so that agents can reliably pick the correct one for common finance tasks.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since this server uses OAuth 2.1 via Clerk, consider explicitly documenting in the JSON manifest the exact auth flow details (auth URL, token URL, scopes, and required headers) so client implementations don’t have to guess how to obtain and attach credentials.
- With 33 tools exposed, it may be worth grouping or namespacing related tools (e.g., budgeting, tax, accounting) in the manifest and ensuring their names/descriptions are narrowly scoped so that agents can reliably pick the correct one for common finance tasks.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}