Title: Connecting Jetpack to WordPress.com via CLI
Last modified: August 22, 2016

---

# Connecting Jetpack to WordPress.com via CLI

 *  [Brandon Yap](https://wordpress.org/support/users/byap00/)
 * (@byap00)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/)
 * I’m trying to connect a multisite’s Jetpack install to WordPress.com via CLI.
   Does anyone know if this is possible?
    I know installing Jetpack is possible 
   via wpcli, but I can’t find a way to connect it to WordPress.com via CLI instead
   of having to go into wp-admin and manually hooking the two together. I’m coming
   from the point of view of automation where we’d like to roll out sites with Jetpack
   that auto connect to WordPress.com Thanks!
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [indietravel](https://wordpress.org/support/users/indietravel/)
 * (@indietravel)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/#post-5864171)
 * +1 for adding this to WP CLI.
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [11 years, 2 months ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/#post-5864249)
 * I’m afraid that’s not possible at the moment. You can activate and deactivate
   modules and you can disconnect Jetpack via WP CLI, but we haven’t added the option
   to connect to a WordPress.com account.
 * If you were to connect a site to WordPress.com via the command line, it’d be 
   hard to handle things like authenticating on WordPress.com or create a WordPress.
   com account from CLI.
 * Do you have any preferences of how this should look like?
 *  [covienam](https://wordpress.org/support/users/covienam/)
 * (@covienam)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/#post-5864256)
 * Hi Jeremy,
 * Would it be easier it we assume that a valid WordPress.com account must be provided
   to the CLI, therefore it wouldnt be necessary to try to create one?
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [11 years, 1 month ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/#post-5864258)
 * While that would remove one part of the process, you would still need to authenticate
   to WordPress.com and accept the connection to your site from CLI.
 * > I’m coming from the point of view of automation where we’d like to roll out
   > sites with Jetpack that auto connect to WordPress.com
 * This seems like something we could add to the existing Jetpack menu in Multisite
   network admin. I took note of it and we’ll consider it next time we iterate on
   the different Jetpack options available to Super admins in Multisite networks.
   [Module management](https://github.com/Automattic/jetpack/issues/866) is also
   something we would like to work on.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Connecting Jetpack to WordPress.com via CLI’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [cli](https://wordpress.org/support/topic-tag/cli/)

 * 4 replies
 * 4 participants
 * Last reply from: [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/connecting-jetpack-to-wordpresscom-via-cli/#post-5864258)
 * Status: not resolved