JobNimbus MCP Server

Created By
clykins90a year ago
Overview

What is JobNimbus MCP Server?

JobNimbus MCP Server is a server designed to interact with the JobNimbus API, enabling AI assistants like Cursor and Claude to access and manipulate JobNimbus data such as Contacts, Jobs, Tasks, Products, Workflows, and Invoices through standardized tools.

How to use JobNimbus MCP Server?

To use the JobNimbus MCP Server, you need to set it up with your AI assistant by following specific configuration instructions for either Cursor or Claude, including providing your JobNimbus API key for secure access.

Key features of JobNimbus MCP Server?

  • Integration with JobNimbus API for AI assistants.
  • Supports various JobNimbus data types (Contacts, Jobs, etc.).
  • Easy setup using npx for running the server.
  • Implements multiple MCP tools for different JobNimbus API endpoints.

Use cases of JobNimbus MCP Server?

  1. Automating job management tasks through AI assistants.
  2. Accessing and updating JobNimbus contacts via voice commands.
  3. Generating invoices and managing workflows using AI tools.

FAQ from JobNimbus MCP Server?

  • What is required to run the JobNimbus MCP Server?

You need Node.js, npm, and your JobNimbus API key to set up the server.

  • Can I use this server with any AI assistant?

Currently, it is designed for use with Cursor and Claude, but it may work with other MCP-compatible clients.

  • Is there any cost associated with using JobNimbus MCP Server?

The server is open-source and free to use under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
clykins90
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago