Optibot

ai.getoptimalPublished by getoptimal.aiv1.4.1Updated Oct 24, 2026

AI code review for your AI assistant — review local changes, branch diffs, and patch files.

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: ai.getoptimal/optibot
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to getoptimal.ai. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.getoptimal%2Foptibot.svg)](https://sourceweft.com/mcp/ai.getoptimal%2Foptibot?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Optibot brings AI code review into an assistant: it reviews local changes, branch diffs and patch files from the desktop.

What you can do: Review local uncommitted changes in a working copy
Review diffs between branches
Review patch files
Authenticate either with an API key or through a browser-based login tool
When to use it: Useful when you want an AI assistant to check code changes before committing or merging, and prefer a dedicated review service over ad-hoc reading of diffs.
Requirements: Runs as a local stdio process installed from the npm package @optimalai/optibot-mcp, so Node.js is needed. Desktop only; no web execution. Authentication is either the OPTIBOT_API_KEY environment variable or the login tool for browser-based OAuth.

Before you install

The server sends your code changes and diffs to the Optibot service for review, so review what leaves your machine. The OPTIBOT_API_KEY is a secret credential; keep it out of shared configuration. Browser-based login opens an OAuth flow.

Installation

In SourceWeft

Open Optibot in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.4.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.