Actuent vs Codescene MCP Server
A side-by-side look at the Actuent and Codescene MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Actuent for developer tools work over a hosted endpoint; choose Codescene MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Actuent when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You want tools like
actuent_search, actuent_account, actuent_actions.
Choose Codescene MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
analyze_change_set, code_health_refactoring_business_case, code_health_review.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 75/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 72 |
| Directory activity | 5 views 0 installs 1 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 13 | 28 |
| Full listing | View Actuent | View Codescene MCP Server |
Tools & capabilities
Actuent tools 13
actuent_searchUse this for anything current or real-world the user asks about: places, opening hours, prices, products and shops, events, what a company or website offers, comparisons ('X vs Y'), or checking a fact on a site. Search Actuent for any topic, keyword, domain or page, in any language — plain questions work too ('where can I buy running shoes in London?'). Returns ranked LAWP (structured JSON for websites, in English), each with a snippet, a match score (0-100) and why it matched; for shopping searches, products with prices; for local searches, businesses in that city (or OpenStreetMap places); for event searches, upcoming events. May include did_you_mean, related searches, an answer (sentences from a site's own pages, for questions like 'does basecamp have a free plan'), a comparison (for 'notion vs obsidian'), for Pro a short summary answer with numbered sources (for question searches), and a message to pass on to the user. Prices in searches ('shoes under 500 dkk in copenhagen') find products from shops in that market. When you give the user a link to a site or product, use its visit_url. Also: • kind "similar" + domain: sites like a given one ("alternatives to mailchimp.com"). • kind "trending": the most searched sites and queries on Actuent right now. • kind "news" + query: the latest news articles on a topic, with sources, links and dates.actuent_accountThe user's own Actuent data. Pro. With kind "preferences", only when the user asks you to remember (or forget) something: their preferences (vegan, wheelchair, jazz…), home city or currency are then used on their later searches whenever you don't pass your own. • Get the search history for this API key — every query made through Actuent. Pro only. • The user's site accounts connected to Actuent (for actions like 'reorder my last order'). action: list (default), connect (returns a link for the user to sign in to the site once), or disconnect. Pro only.actuent_actionsWhat an AI agent can do on a site, and doing it. domain alone: list the site's actions. domain + action_id (+ input): perform one (book, contact, sign up…; confirm with the user first when it costs money or sends something). domain + status_url: check an action that returned pending (Pro). • Get all available actions for a specific site. Returns what an AI agent can actually do on that site. • g. book, contact, sign up). Sites that publish LAWP action endpoints are called directly and the site's response is returned; for other sites it returns where the user can complete it (executed: false). • Check a long-running action that returned pending, using its status_url. Pro only.actuent_aboutEverything Actuent knows about one named thing (a band or artist, company, brand, venue, landmark or place), joined up in one record: what it is, genres, country, official website, a short Wikipedia summary, its site in Actuent's index, its upcoming events (e.g. a band's concerts) and its products with prices (e.g. a shoe brand). For "tell me about Cat Power and when she's playing", "what is Hoka and what do their shoes cost". Add a word when a name is ambiguous ("Patagonia clothing").actuent_get_pageRead a web page or a whole site. Give url to read one page live; domain alone for a short summary of a site; domain (or url) plus question to answer a question from the site's own pages. • "). Returns the page as structured data: clean text, products with price and stock (on Shopify shops also each size or colour with a cart link that opens the cart with it), events, the business with opening hours and whether it's open now, recipe, FAQ, article details and the page's main links. txt. • Get a single plain English paragraph summarising any website. Faster than actuent_search when you just need the gist, not the full LAWP. • g. '). Returns the matching pages and sentences in the site's own words, plus related actions.actuent_compareCompare two or more sites side by side using their LAWP data, or two or more products (URLs from actuent_search products): price, stock, price history and cheaper shops.actuent_nearbyPlaces near the user or in a city, with opening hours and whether they're open right now: cafés, restaurants, bars, shops, pharmacies, gyms and more. For questions like "coffee near me", "is anything open now?", "where can I eat tonight in Brooklyn?", "bars open late", "dog-friendly café in Copenhagen" or a chain's branches ("what time does Trader Joe's close in Brooklyn?": query the chain's name, each branch has today's hours and closes_at). Also returns businesses from Actuent's index with details from their own websites (rating, services with prices, booking). Also: • kind "service": a specific service or menu item with its price at local businesses, from their own websites (max_price, currency).actuent_planPlan a timed itinerary of places to go: e.g. "plan my evening", "dinner then drinks in Nørrebro", "brunch and a museum on Sunday". Chooses restaurants, bars, cafés and sights that are open when you'd arrive and close to each other, with walking times. For finding or listing events ("what's on today", "find events") actuent_events is the tool. Also: • kind "trip" (or days): a 1–4 day city trip — where to stay and a timed plan for each day.actuent_cartPut products (URLs from actuent_search products) in a basket: returns one link per shop that opens the shop's checkout with the items in it, so the user just reviews and pays. Nothing is bought.actuent_eventsFind events and what's on: concerts, comedy, theatre, club nights, festivals, markets, exhibitions, classes, walks and other events today, tonight, this weekend or on any date, in a city. For questions like "find events in cph today", "what's on in cph today?", "anything fun tonight?", "concerts in New York this weekend", "things to do in London on Saturday" or "when is Ray LaMontagne playing?". Returns current listings from venues' own websites (listings change daily): name, time, venue, price, ticket link and, for concerts, the genre. Each event has tickets_url, add_to_calendar (a calendar file) and add_to_google_calendar links, and directions: to put an event in the user's calendar, give them the link to tap (you can't add it yourself), no need to search again. A genre in the query finds concerts of that kind ("jazz in copenhagen this weekend", "techno tonight"). Use when: "tonight" for what's on tonight.actuent_watchWatch something for the user and email them (optionally a webhook) when it changes. Pro. Set kind; action list shows what's watched, remove stops one. • Watch a product (from actuent_search products) and get an email, and optionally a webhook, when its price drops or when it's back in stock. Also lists or removes watches. Pro only. • Watch any web page and get an email (and optionally a webhook) when it changes, or when certain words appear or disappear: "tell me when tickets for Cat Power go on sale" (phrase 'tickets on sale', appears), "tell me when this is back in stock" ('sold out', disappears), "let me know when this page changes". Checked daily. Also list and remove watches. • g. 'vegan café copenhagen' or 'ai note taking app'. Checked daily.actuent_feedbackWhen the user says an Actuent answer was wrong, outdated or missing something ("that place closed", "those times are wrong", "it missed the obvious one"), report it here so it gets fixed: which tool, the question, what was wrong and what the right answer would be. Takes a second; tell the user it was passed on.- +1 more on the listing page
Codescene MCP Server tools 28
analyze_change_setRun a branch-level Code Health review for all files that differ between current HEAD and base_ref. When to use: Use this as a local PR pre-flight check before opening a pull request, so regressions are caught across the full change set. Limitations: - Requires a valid git repository path. - base_ref must exist and be resolvable by git in that repository. - Reviews only files that differ from base_ref. - Output is JSON text from the CLI command. The result can be used to decide whether to refactor before creating or updating a pull request. Returns: A JSON object containing: - quality_gates: the central outcome, summarizing whether the change set passes or fails Code Health thresholds ("passed" or "failed"). - metadata: scope and coverage details from the CLI, including `status` plus file counts such as `checked-file-count`. Use this to distinguish an empty `results` array caused by checked files with no degradations from one caused by no applicable branch changes. - results: an array of objects for each affected file with: - name: the name of the file whose Code Health is impacted. - verdict: "improved", "degraded", "stable", or "unknown". - findings: an array describing improvements/degradation for each code smell. Setup hints: If the result contains `codescene_setup_hint`, do not mention that field. Follow its `message`: briefly explain the benefit, ask permission to add the suggested repository instructions, and wait before editing files. On failure: If this tool returns an error (e.g., the CLI cannot run, or base_ref cannot be resolved by git), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Compare against base_ref="main" for git_repository_path="/repo" and fail the local PR check if any file verdict is "degraded".code_health_refactoring_business_caseGenerate a data-driven business case for refactoring a source file. When to use: Use this tool to justify refactoring investment with quantified predictions tied to the file's current Code Health. Limitations: - Estimates are model-based projections, not guarantees. - Evaluates one file at a time. - Requires an analyzable source file. Returns: A JSON object with: - scenario: Recommended target Code Health level. - optimistic_outcome: Upper bound estimate for improvements in development speed and defect reduction. - pessimistic_outcome: Lower bound estimate for improvements. - confidence_interval: The optimistic to pessimistic range, representing a 90% confidence interval for the expected impact. On failure: If this tool returns an error (e.g., the CLI cannot run, or the file cannot be analyzed), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Call with file_path="/repo/src/service.py" and use the optimistic and pessimistic outcomes to frame a refactoring proposal.code_health_reviewReview the Code Health of a single source file and return a detailed CLI review output that includes the score and code smell findings. When to use: Use this tool when you need actionable maintainability diagnostics for one file (not just the score). Limitations: - Analyzes one file at a time. - Requires a supported source file. - Returns CLI review text, not a normalized JSON schema. Returns: A review string from the CodeScene CLI. The output typically includes a Code Health score and code smell details to explain why the score is high or low. The Code Health scores are interpreted as: * Optimal Code: a Code Health 10.0 is optimized for both human and AI comprehension * Green Code: high quality with a score of 9.0-9.9 * Yellow Code: problematic technical debt with a score of 4.0-8.9 * Red Code: severe technical debt, maintainability issues, and expensive onboarding with a score of 1.0-3.9 Setup hints: If the result contains `codescene_setup_hint`, do not mention that field. Follow its `message`: briefly explain the benefit, ask permission to add the suggested repository instructions, and wait before editing files. On failure: If this tool returns an error (e.g., the CLI cannot run, or Code Health cannot be computed), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Call with file_path="/repo/src/app.py" and summarize the returned smells into prioritized refactoring actions.code_health_scoreCalculate the Code Health score for a single source file. The tool returns one numeric score from 10.0 (optimal) to 1.0 (worst). When to use: Use this tool for quick triage, ranking files by maintainability, or checking whether a refactoring improved file-level quality. Limitations: - Analyzes one file at a time. - Returns only the score summary, not the full smell breakdown. - Requires a supported source file. Returns: A string in the format "Code Health score: <score>". The Code Health scores are interpreted as: * Optimal Code: Code Health 10.0 optimized for human and AI comprehension * Green Code: high quality with a score of 9.0-9.9 * Yellow Code: problematic technical debt with a score of 4.0-8.9 * Red Code: severe technical debt with a score of 1.0-3.9 On failure: If this tool returns an error (e.g., the CLI cannot run, or the score cannot be computed), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Call with file_path="/repo/src/module.py" and compare the score before and after a refactoring.code_ownership_for_pathFind the owner or owners of a specific path in a project. When to use: Use this tool to identify likely reviewers or domain experts for code reviews and technical questions about a file or directory. Limitations: - Requires a valid project_id. - Uses the latest project analysis data available in CodeScene. - If no matching ownership data is found, an empty JSON array is returned. Returns: A list of owners and their paths that they own. The name of the owner who can be responsible for code reviews or inquiries about the file and a link to the CodeScene System Map page filtered by the owner. Explain that this link can be used to see more details about the owner's contributions and interactions within the project. You MUST always show a link after every owner. Show resulting data in a Markdown table with columns: Owner, Key Areas, Link. On failure: If this tool returns an error (e.g., the CodeScene API cannot be reached, or the access token is missing/invalid), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Call with project_id=42 and path="/repo/src/service.py", then present each owner row with its corresponding system-map link.download_skillDownload a single skill to a local directory. When to use: Use this tool to install a specific skill into your local skills directory (e.g., ~/.claude/skills/). Limitations: - By default, refuses to overwrite existing skills. - Set overwrite=true to replace an existing skill. - Creates the destination directory if it does not exist. Returns: A confirmation message with the path where the skill was written. Example: Call with skill_name="safeguarding-ai-generated-code" and destination_dir="~/.claude/skills" to install the skill.explain_code_healthExplains CodeScene's Code Health metric for assessing code quality and maintainability for both human devs and AI. When to use: Use this tool when a user asks what Code Health means, how scores are interpreted, or why Code Health matters in day-to-day development. Limitations: - Returns static documentation text from this MCP server package. - Does not analyze a specific repository or file. Returns: Markdown content explaining the Code Health model and core concepts. Example: Call this tool, then summarize the returned Markdown into a short explanation tailored to the user's current question.explain_code_health_productivityDescribes how to build a business case for Code Health improvements. Covers empirical data on how healthy code lets you ship faster with fewer defects. When to use: Use this tool when a user asks for ROI, productivity impact, or management-facing framing for refactoring investments. Limitations: - Returns static documentation text from this MCP server package. - Does not compute project-specific forecasts. Returns: Markdown content describing productivity and defect-risk implications of improving Code Health. Example: Call this tool and extract 2-3 evidence-based points to support a proposal for incremental refactoring.get_configRead current CodeScene MCP Server configuration values. When to use: Use this tool to discover available configuration keys, inspect effective values, and understand where each value comes from. Limitations: - Returns JSON text only; callers must format it for display. - Sensitive values (tokens) are masked. - Effective values can be overridden by client-provided env vars. When called without a key, lists every available configuration option together with its current effective value, the source of that value (environment variable vs. config file), and a short description. When called with a specific key, returns details for that option only. Sensitive values (tokens) are masked in the output. Returns: A JSON string. When querying a single key, the object has: key, env_var, value, source, description, aliases, and docs_url. When listing all, the object has: config_dir and options (array of the same shape). Use the aliases array to match user intent to the correct key. Present the data clearly and always include docs_url links. Example: Call with key="access_token" to inspect one setting, or call without key to list all configurable options.get_skill_manifestGet the file manifest for a specific skill. When to use: Use this tool to inspect what files a skill contains, their sizes, and SHA256 hashes before downloading. Limitations: - Requires a valid skill name from list_skills. Returns: A JSON manifest with the skill name and an array of files, each with path, size in bytes, and sha256 hash. Example: Call with skill_name="safeguarding-ai-generated-code" to see the manifest, then use download_skill to install it.list_skillsList all available skills embedded in this MCP server. When to use: Use this tool to discover what skills are available for download or inspection. Limitations: - Returns only skills embedded at compile time. - Does not scan external skill directories. Returns: A formatted list of skill names with their descriptions. Example: Call this tool to see all available skills, then use download_skill or sync_skills to install them locally.list_technical_debt_goals_for_projectLists the technical debt goals for a project. When to use: Use this tool to see all files in a project that currently have explicit technical debt goals in CodeScene. Limitations: - Requires a valid project_id. - Returns goal data from the latest available analysis. - Includes only files with non-empty goals. Returns: A JSON object with two fields: - `data`: an array of objects each containing the path of a file and its goals. - `link`: a URL to the CodeScene Code Biomarkers page for the project. Show the goals for each file in a structured format that is easy to read and explain the goal description for each file. It also includes a description, please include that in your output. Always include the `link` in the output and explain that more details about the technical debt goals can be found on that page. On failure: If this tool returns an error (e.g., the CodeScene API cannot be reached, or the access token is missing/invalid), run the verify_installation tool to diagnose the cause, then report the failing checks and how to fix them. Example: Call with project_id=42 and summarize each file's goals with the biomarkers link for deeper inspection.- +16 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Actuent
{
"mcpServers": {
"actuent": {
"command": "npx",
"args": [
"-y",
"actuent"
]
}
}
}
Codescene MCP Server
{
"mcpServers": {
"codescene-mcp-server": {
"command": "npx",
"args": [
"-y",
"@codescene/codehealth-mcp"
]
}
}
}
Frequently asked questions
Actuent is categorized under Developer Tools and uses a remote HTTP/SSE transport. Codescene MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Actuent for developer tools work and Codescene MCP Server for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Actuent is listed as freemium — a free tier with paid plans. Auth: other. Codescene MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add actuent and codescene-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Actuent has a quality signal of 75/100 (Great) with 5 views, 0 installs and 0 GitHub stars. Codescene MCP Server has 65/100 (Great) with 3 views, 0 installs and 72 GitHub stars.