Deploy and Host Google Drive MCP on Railway

Google Drive MCP (specifically the google-docs-mcp package) is an open-source Model Context Protocol server that grants AI assistants full read, write, and administrative access to your Google Suite. It natively connects AI agents to Google Docs, Sheets, Drive, Gmail, and Calendar to automate cross-workspace workflows.

About Hosting Google Drive MCP

Deploying the Google Drive MCP server on a cloud platform like Railway enables seamless, remote AI integration without requiring local installations or token management for every user. The process involves creating a Google Cloud OAuth Client, configuring the necessary API scopes across your Google Workspace, and passing those credentials to your Railway instance. By running the server in the cloud, it utilizes an HTTP stream (streamableHttp) transport protocol rather than standard local I/O. This setup delegates the authentication flow directly to the remote server, meaning the MCP client will automatically trigger a Google sign-in prompt on the user's first connection, making it ideal for team-wide AI deployments.

Common Use Cases

• Reading, searching, generating, and organizing markdown documents and folders dynamically across Google Drive.
• Manipulating Google Sheets by writing data ranges, updating formatting, adding conditional logic, and reading native cell values.
• Automating inbox triage by reading unread Gmail threads, generating drafts, or instantly scheduling and modifying Google Calendar events.

Dependencies for Google Drive MCP Hosting

• Google Cloud Console Account (to generate OAuth Client credentials and enable APIs).
• Railway Account (for cloud deployment, environment variable configuration, and hosting).
• An MCP Client (such as Claude Desktop, Cursor, or Windsurf) to connect to the deployed Railway URL.

Deployment Dependencies

To get the required GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, follow these exact steps:

1. Go to the Google Cloud Console.
2. Create a new project or select an existing one.
3. Enable the following APIs: Google Docs API, Google Sheets API, Google Drive API, Gmail API, and Google Calendar API.
4. Configure the OAuth consent screen: Select "External", add your email as a test user, and ensure you add the gmail.modify and calendar.events scopes alongside the standard Docs, Sheets, and Drive scopes.
5. Create an OAuth client ID and select Desktop app as the application type.
6. Copy the generated Client ID and Client Secret from the confirmation screen.

Implementation Details

To deploy this on Railway, link the GitHub repository and configure the following Environment Variables in your Railway project settings:

MCP_TRANSPORT=httpStream
BASE_URL=https://
GOOGLE_CLIENT_ID=your_client_id_here
GOOGLE_CLIENT_SECRET=your_client_secret_here
JWT_SIGNING_KEY=your_secure_random_secret_key

Once the service is active on Railway, add the following configuration to your MCP client's configuration file (e.g., claude_desktop_config.json):

{
  "mcpServers": {
    "google-docs": {
      "type": "streamableHttp",
      "url": "https:///mcp"
    }
  }
}

Why Deploy Google Drive MCP on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Google Drive MCP on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.