Drivara

io.github.bsrishiPublished by GitHub account bsrishiv1.0.0Updated Oct 24, 2026

Read-only access to your Drivara fleet — jobs, drivers, vehicles, fuel, profit & analytics.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server giving an assistant read-only access to a Drivara fleet account: jobs, drivers, vehicles, fuel, profit and analytics.

What you can do
Read fleet jobs and their details from the connected Drivara account. Look up drivers and vehicles on record. Review fuel records. Consult profit figures and fleet analytics. All access is described as read-only, so the assistant can report on fleet data but not change it.
When to use it
Useful when you want an assistant to answer questions about a Drivara fleet — job status, driver and vehicle records, fuel use, profit or analytics — without opening the Drivara app yourself.
Requirements
A remote endpoint at app.drivara.in reached over streamable HTTP. OAuth sign-in with a Drivara account is required; no environment variables or headers are declared. Network access is needed.
Before you install
Access is tied to your Drivara account through OAuth, so the assistant can see whatever fleet data that account covers, including drivers, vehicles, fuel and profit figures. The description states read-only access, but confirm the granted scope during sign-in before connecting.

Installation

In SourceWeft

  1. Open Drivara in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bsrishi%2Fdrivara/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "drivara": {
      "type": "http",
      "url": "https://app.drivara.in/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.