Today, Vantage is expanding the MCP Connectors library for the FinOps Agent with three new connectors: Linear, Notion, and GitHub. Customers can now bring engineering knowledge, planned work, and code context into the same conversation as Vantage cost data, and turn FinOps findings into action, such as creating Linear tickets or GitHub issues.

Connect Linear, Notion, and GitHub to the FinOps Agent to investigate costs with context from across the development lifecycle.

When Vantage launched MCP Connectors in June, the goal was to connect the systems of record customers use to power their businesses with Vantage, the FinOps system of record for cloud, SaaS, and AI spend. Datadog, the first supported MCP connector, added operational signals that help explain why costs changed. It was our goal to expand to other sources of context that live in tools like company knowledge bases, issue trackers, and code repositories. These systems can both provide context for agent-led investigations and serve as destinations for assets created from FinOps Agent conversations.

Now, with the new MCP connectors of Linear, Notion, and GitHub, the Vantage Agent can expand context of conversations across the development lifecycle, as well as create resources such as Notion documents, Linear issues, and GitHub issues. Each connector is enabled from the MCP Connectors section of the Integrations page. Once an Owner or Integration Owner first enables the connector for the Vantage organization, individual users can then authorize their own Linear, Notion, or GitHub account from the Integrations page. Once enabled, the FinOps Agent can reference company knowledge bases or create monthly cost summaries in Notion, find or create related work in Linear, and examine selected GitHub repositories, issues, and pull requests. Connecting these MCPs gives the FinOps Agent the context to understand not only what changed in a customer's spend, but also what the affected system does, who owns it, whether related work is already underway, and where a change may need to be made. For example, a team investigating an unexpected increase in Kubernetes spend can ask the agent to identify the affected services in Vantage, retrieve the architecture and ownership model from Notion, check Linear for related migration work, and inspect the relevant GitHub repositories for recent changes. If work is needed to remediate these costs, the agent can create a Linear or GitHub issue that includes the underlying cost context. The same connected context is available to Canvas reports for persistent analysis beyond a single conversation.

Linear, Notion, and GitHub are available as MCP Connectors today for all Vantage customers. To get started, navigate to the Integrations page and select a connector from the MCP Connectors section. Refer to the FinOps Agent documentation for configuration details and the FinOps AI Prompt Guide for example queries.

Frequently Asked Questions

1. What is being launched today?

Vantage is adding Linear, Notion, and GitHub to the MCP Connectors library for the FinOps Agent. Customers can use these connectors alongside Vantage cost data in the same Agent conversation or Canvas to bring in development context and, when explicitly requested, take supported actions such as creating or updating GitHub issues, Linear tickets, or Notion pages.

2. Who is the customer?

This feature is available to all Vantage customers utilizing the FinOps Agent or Canvases.

3. How much does this cost?

Charges are based on token consumption for conversations with the FinOps Agent through natural language. Vantage will waive all costs associated with token consumption during an introductory period. Detailed pricing information will be announced before billing begins. Once token consumption billing begins, total costs accumulated and tokens consumed will be available on the Billing page and will be billed monthly, either via credit card or AWS Marketplace. To learn more about pricing examples, head to the new portion of the pricing page.

4. What Vantage permissions are needed to enable an MCP connector?

An Owner or Integration Owner must enable a connector for the Vantage organization. Once enabled, any individual Vantage users can authorize their own accounts regardless of role. Editors and Viewers can access the MCP Connectors section of the Integrations page when at least one user-authorized connector is enabled for their organization; they do not gain access to manage unrelated integrations.

5. How do I connect Linear, Notion, or GitHub?

Once an Owner or Integration Owner enables the connector, each Vantage user then authenticates through the Integrations page. Each user will sign in to the application through a dedicated authorization page, and return to Vantage once the MCP Connector is authenticated.

6. Why does each user need to authorize an account?

The FinOps Agent acts with the requesting user's permissions. Per-user authorization prevents one person's access from being shared with everyone in the Vantage organization and ensures supported write actions are attributed to the person who requested them. For GitHub, the agent is further limited to the repositories selected through the Vantage GitHub App.

7. Can I use multiple MCP connectors in the same conversation or Canvas?

Yes. The FinOps Agent can use any combination of enabled, authorized connectors together with Vantage data. The agent selects the relevant tools based on the request; users do not need to manually choose a connector for each prompt.

8. What data does Vantage access, and does it store any of it?

The FinOps Agent requests data from a connector only when needed to answer a prompt or refresh a Canvas. Linear and Notion data is stored only when it is explicitly written into a saved Agent conversation response or Canvas report. For GitHub, Vantage stores only metadata for selected repositories, such as customer-provided repository descriptions and auto-generated repository summaries for repository context, but does not persist any source code. Credentials are encrypted and are not exposed to the model.

9. Is data from MCP connectors used to train models?

No. Data retrieved through MCP Connectors is not used to train models by Vantage or its underlying model providers.

10. What happens if an MCP connector is disconnected or its authorization expires?

The FinOps Agent can no longer use that user's connector credentials. If authorization expires or is revoked, Vantage surfaces a reconnect prompt. Notion authorizations expire after 180 days or after 30 days of inactivity; periodic reconnection is expected. Historical conversations retain prior responses according to the organization's retention settings, but the agent cannot make new connector calls until access is restored.

---

Linear

11. What can I do with the Linear MCP connector?

• Find existing work: Search issues, projects, teams, comments, and related activity for a service, anomaly, recommendation, or cost initiative.
• Create and update issues: Turn a cost anomaly, budget overrun, or optimization recommendation into tracked work with Vantage context included, and add comments to collaborate with the engineering team.
• Identify ownership: Use Linear teams, projects, and assignments to determine who owns the next step.
• Connect execution to outcomes: Compare Linear issues completed per user with their token consumption in AI tools.

12. Which tools are available through the Linear MCP connector?

The Linear MCP connector currently provides the following tools. Linear manages this inventory and may add, remove, or rename tools over time. Availability is also subject to the authorizing user's Linear permissions.

• Search and workspace: fetch, search, search_documentation, get_workspace, get_user, list_users, get_team, list_teams
• Work planning: get_issue, list_issues, save_issue, share_issue, unshare_issue, get_issue_status, list_issue_statuses, create_issue_label, list_issue_labels, list_project_labels, list_cycles, get_project, list_projects, save_project, get_milestone, list_milestones, save_milestone, get_initiative, list_initiatives, save_initiative, create_initiative_label, list_initiative_labels
• Documents, comments, updates, and attachments: get_document, list_documents, save_document, list_comments, save_comment, delete_comment, get_status_updates, save_status_update, delete_status_update, create_attachment, create_attachment_from_upload, delete_attachment, extract_images, get_attachment, prepare_attachment_upload
• Customers: list_customers, save_customer, delete_customer, save_customer_need, delete_customer_need
• Releases: get_release, list_releases, save_release, get_release_note, list_release_notes, save_release_note, list_release_pipelines
• Code reviews and diffs: get_diff, list_diffs, get_diff_threads, save_diff_comment, delete_diff_comment, resolve_diff_thread, submit_diff_review, merge_diff
• Agent skills: get_agent_skill, list_agent_skills

13. What Linear permissions are required?

Any Linear user can authorize the connector. The FinOps Agent can only see and act on content that the authorizing user is permitted to access in Linear.

14. Can the FinOps Agent take write actions in Linear?

Yes. The Linear connector can create and update issues, add comments, and perform other supported actions when the user explicitly requests them. Actions are limited by that user's Linear permissions and are attributed to the authorizing user.

15. Can I connect the Linear MCP using an API key or a pre-generated OAuth token?

No. Vantage does not support authenticating to the Linear MCP with an API key or pre-generated OAuth token. Each user must connect through the standard interactive OAuth flow.

---

Notion

16. What can I do with the Notion MCP connector?

• Add architecture and ownership context: Retrieve documentation that explains a service, system, or responsible team during a cost investigation.
• Use runbooks and decisions: Reference operational guidance or past decisions when evaluating an anomaly or recommendation.
• Create documentation: Create a page that serves as an executive cost summary, summarizes a cost investigation, or lists optimization opportunities for teams to review.
• Connect knowledge to cost: Combine structured or unstructured Notion content with current Vantage data in one response.

17. Which tools are available through the Notion MCP connector?

The Notion MCP connector currently provides the following tools. Notion manages this inventory and may add, remove, or rename tools over time. Some tools also require particular Notion plans or workspace settings.

• Search and retrieval: notion-search, notion-fetch, notion-list-private-pages, notion-list-shared-pages, notion-list-favorite-pages, notion-list-recent-pages, notion-search-agents
• Pages and organization: notion-create-pages, notion-update-page, notion-move-pages, notion-duplicate-page, notion-convert-page-to-skill, notion-create-folder, notion-update-folder
• Databases and views: notion-create-database, notion-update-data-source, notion-create-view, notion-update-view, notion-query-data-sources
• Meetings and comments: notion-query-meeting-notes, notion-create-comment, notion-get-comments
• Files: notion-create-file-upload, notion-create-attachment, notion-download-attachment
• Workspace information: notion-get-teams, notion-get-users
• Async operations: notion-get-async-task

18. What Notion content can the FinOps Agent access?

The connection is scoped to the authorizing user's existing Notion access. The FinOps Agent respects that user's page and database permissions and can only read or write content they could access directly in Notion. Searching across apps connected to Notion requires a Notion AI plan. Enterprise workspaces using Notion MCP Governance must add Vantage to their AI apps allowlist before members can connect.

19. Can the FinOps Agent write to Notion?

Yes. The connector can create and edit text-based Notion content when explicitly requested, subject to the authorizing user's access. Notion's hosted MCP server does not currently support uploading images or files through the connector.

---

GitHub

20. What can I do with the GitHub MCP connector?

• Inspect repository context: Search approved repositories and examine code and repository information related to a cost-driving service or resource.
• Review engineering activity: Find relevant issues, pull requests, and GitHub Actions activity that may explain a change in spend.
• Create tracked work: Search for an existing issue and, when needed, create a GitHub issue with the Vantage cost context included.
• Support remediation workflows: Use code context alongside Vantage recommendations, including existing infrastructure-as-code workflows.

21. Which tools are available through the GitHub MCP connector?

Vantage currently enables read-only tools from GitHub's repository, issue, pull request, and Actions tool groups, together with three Vantage-specific GitHub tools. GitHub manages its hosted tool inventory and may add, remove, or rename tools over time. Tool availability remains limited by the repositories selected for Vantage and the authorizing user's GitHub permissions.

• GitHub Actions: actions_get, actions_list, get_job_logs
• Issues: get_label, issue_read, list_issue_fields, list_issue_types, list_issues, search_issues
• Pull requests: list_pull_requests, pull_request_read, search_pull_requests
• Repositories: get_commit, get_file_contents, get_latest_release, get_release_by_tag, get_tag, list_branches, list_commits, list_releases, list_repository_collaborators, list_tags, search_code, search_commits, search_repositories
• Vantage-specific GitHub tools: get-github-repos, locate-terraform-resource, create-terraform-issue

22. How is GitHub access configured?

GitHub has two layers of access. A Vantage Owner or Integration Owner enables the connector, and a GitHub Organization Owner installs the Vantage GitHub App. The Vantage Owner or Integration Owner then selects the repositories available to the organization. Each Vantage user authorizes their own GitHub account. The FinOps Agent can act only within both boundaries: the repositories selected for Vantage and the authorizing user's GitHub permissions.

23. Can the FinOps Agent take write actions in GitHub?

Yes. The GitHub connector can create and update issues when explicitly requested. Issue creation is user-triggered, and the FinOps Agent asks for confirmation before creating an issue. Vantage does not create pull requests; customers can assign a Vantage-created issue to an engineer or GitHub Copilot in GitHub. All actions remain limited by repository selection, the user's GitHub permissions, and the FinOps Agent's tool-level safeguards.

24. How does this relate to Vantage's existing GitHub integration?

The launch expands GitHub from a specialized infrastructure-as-code remediation integration into a general MCP Connector available to Agent conversations and Canvas. Vantage preserves the existing GitHub App installation and repository selection model, as well as the existing Terraform remediation workflow, while adding the GitHub MCP Connector to use in Agent conversations and Canvases.