Fluent MCP MCP Server

If you already use Fluent MCP, the fluent mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Fluent (ServiceNow SDK).

What the server does

This MCP server implements the Model Context Protocol specification with the following capabilities:

• SDK Command Tools — - sdk_info plus ServiceNow SDK command tools for init, build, install, dependencies, transform, download, clean, pack, explain, and query
• Rich Resources — - API specifications, instructions, and code snippets for 65 ServiceNow metadata types
• API Documentation Lookup — - explain_fluent_api returns SDK docs for any Fluent API or guide — no project required
• Lazy Auto-Authentication — - Detects and caches an auth profile only when an auth-requiring command or check_auth_status needs it
• Explicit Project Context — - Resolves each project command from its workingDirectory argument, the initialized session, or FLUENT_MCP_WORKING_DIR, then fails with actionable guidance instead of guessing
• Client-Friendly Schemas — - Optional inputs advertise their canonical value types while the enforced schema accepts null as an omitted-value compatibility form

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• sdk_info — Get SDK version or help
• explain_fluent_api — Look up Fluent SDK documentation for any API or guide. No Fluent project required
• init_fluent_app — Initialize or convert a ServiceNow app. Non-interactive: missing intent-specific arguments fail with an error naming them
• build_fluent_app — Build the application
• deploy_fluent_app — Deploy to a ServiceNow instance. SDK flow activation can be skipped
• fluent_transform — Convert XML or instance metadata to Fluent TypeScript. Local paths do not require auth; instance transforms do
• download_fluent_dependencies — Download dependencies and type definitions
• download_fluent_app — Download metadata from an instance
• clean_fluent_app — Clean output directory
• pack_fluent_app — Create an installable artifact
• query_fluent_records — Read-only Table REST query against an instance; returns a JSON envelope
• get-api-spec — Get an API specification or list all available metadata types

Credentials and setup notes

Configuration is passed through the environment: FLUENT_MCP_WORKING_DIR, SN_INSTANCE_URL, SN_AUTH_TYPE, SN_USER_NAME, SN_PASSWORD, SN_SDK_INSTANCE_URL, SN_SDK_OAUTH_CLIENT_ID, SN_SDK_OAUTH_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fluent MCP's toolset — sdk_info, explain_fluent_api, init_fluent_app and 11 more — is a fair guide to whether it matches your workflow. It is maintained by modesty; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fluent MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.